Brainstorming

Turn a development prompt into a validated Product Requirements Document and design document through natural collaborative dialogue. Run the three stages in order; never skip a validation gate.

Invariants

These hold in every stage:

• Never run git commit without the user's explicit consent. Approval to save an artifact or continue the workflow is not consent to commit.
• Never create an implementation plan.
• Never inspect, edit, or ask about .gitignore. After saving the first artifact, you may say exactly: Consider adding docs/agentic-engineering/ to .gitignore manually.

Stage 1 — Understanding

• Check out the current project state first (files, docs, recent commits). If no repository exists, state that limitation and use the available evidence.
• Before asking detailed questions, assess scope: if the request describes multiple independent subsystems (e.g., "build a platform with chat, file storage, billing, and analytics"), flag this immediately. Don't spend questions refining details of a project that needs to be decomposed first.
• If the project is too large for a single PRD, help the user decompose into sub-projects: what are the independent pieces, how do they relate, what order should they be built? Then run the normal flow on the first sub-project. Each sub-project gets its own PRD → design → plan cycle.
• Ask one focused question at a time until the problem, goals, constraints, and success criteria are materially clear.
• For every clarifying question, provide at least two concrete options. Mark one as Recommended and briefly explain why it best fits the evidence, constraints, or simplest path; keep an open-ended response available when the options do not cover the user's intent.