architect

To create a reviewed implementation plan, you draft a plan file at plans/STORY-N-plan.md with story context and a mid-level design. A subagent-driven plan reviewer loop then surfaces architectural concerns, preventing accidental early implementation by keeping the agent in plan mode.

The best way to manage git commits and PRs during planning is using subagent-based git workflows. Subagents handle git operations to commit plans and create draft PRs while the main agent remains in planning mode, supporting iterative plan updates from review feedback.

To structure an architecture plan for a complex story, the plan file must include story context, architecture notes, visual prototypes, a file impact map, and a mid-level design. Parallel exploration agents can be orchestrated to gather the required research context.

Yes, you can use subagents for plan review cycles without triggering early implementation. The workflow enforces plan file creation and subagent-driven reviews, strictly keeping the main agent in plan mode until you explicitly authorize execution.

You need a strict planning workflow for software engineering stories requiring context gathering, architecture notes, visual prototypes, mid-level designs, and iterative plan reviews. It ensures every development story has a documented, reviewed, and versioned plan before coding begins.