This page walks through generating a Blueprint — your project’s four design documents — reviewing it, and writing it into your repository. For what a Blueprint is and why, start with the Blueprint concept page.
Open Plan > Blueprint
From your project, open Plan, then select Blueprint. If none exists yet, you’ll see the Generate blueprint card.
Generate a draft
In the Generate blueprint card:
- Choose the scenario:
- Greenfield — starting from scratch, an empty repository with no existing code.
- Brownfield — an existing project with code the Blueprint can read from.
- (Optional) Add notes describing anything DIJJI.ai should know, and upload files or screenshots to steer the result. If you’d rather draft the documents yourself first, Download blank templates.
- Select Generate blueprint.
DIJJI.ai drafts the four documents — Tech Stack, Architecture, Design, and QA — showing Generating blueprint… while it works.
Review and correct it
When the draft is ready, the four documents open in the viewer. Read each one, watching the status on every field:
- Filled (green) — nothing needed.
- Assumption — confirm/change (amber) — check the guess; adjust it if it’s wrong.
- Question — answer (blue) — DIJJI.ai needs you to decide.
Each field has a plain-language explanation and a Technical detail disclosure. To change something, use the field’s Want to change this? input to enter a correction.
To refine the whole draft:
- Add input opens a panel to add more context, then Update blueprint.
- After entering corrections in one or more fields, Regenerate redraws the draft with them. (Until you’ve entered a correction, the button reads Regenerate (0) — add a correction first.)
- Earlier versions can be restored from the version control (Restore v{N}?), and the ⋯ menu has Reset / Start over to begin from scratch.
Write it to the repository
Once you’ve cleared the assumptions and answered the open questions, select Write to repo and confirm. (The button stays disabled while open questions or uncleared corrections remain.)
DIJJI.ai renders the four documents to your repository’s /docs folder and opens a pull request — a View pull request link takes you to it. Review and merge it like any other pull request, and the design docs land in your repo alongside the code.
Later, when the project moves on, open the Blueprint again, make your changes, and Write again to update the documents with a fresh pull request.