Skip to main content
This page covers how to read your generated plan and what to look for. Spending 10 minutes reviewing before you build saves an hour later.

​
Read top to bottom

Start at the top of the plan page. Each section is a card you can read independently:
  1. Overview — does the one-paragraph summary match what you intended?
  2. Modules — are the features right? Anything missing or extra?
  3. User types — does each user type’s description match the role you imagined?
  4. System services — are the chosen services (auth, storage) the ones you want?
  5. Integrations — are the third-party services correct?
You will also see a Preview section that renders sample screens. The preview is a quick visual check — if it looks like a different app, the plan probably is.

​
What to look for

  • Missing features. Things you said in your prompt that did not make it into modules. Add them.
  • Hallucinated features. Modules Archie added that you did not ask for. Remove them.
  • Wrong user types. A “guest” type when your app is internal-only. Edit or remove.
  • Wrong integrations. SendGrid when you wanted Resend. Replace.

​
When to edit vs. iterate vs. regenerate

  • Direct edit — small text changes (rename a module, tweak a description) are fastest as direct edits.
  • Plan chat — multi-step changes (“drop the messaging module and add billing”) are easier in the plan chat.
  • Regenerate — if a whole section is off the mark, regenerate that section from the section header. Use this sparingly.
Modules section on the plan page

​
FAQ

Yes. The build takes the whole plan as input, so an unread section becomes guesswork in the output.
For a first project, 10–20 minutes. Once you are used to the format, five.
Open the plan chat and describe what is off. Archie will ask follow-up questions and propose changes.