recipe-plan

To turn design documents into actionable work plans, provide a design document path to initiate the planning workflow. The system orchestrates plan creation, optionally generates test skeletons, and presents a reviewable plan for your approval before implementation.

Yes, you can generate integration and E2E test skeletons alongside a work plan. The planning workflow optionally creates these test skeletons during plan creation, ensuring your implementation milestones are structured and testable from the start.

Approval workflow orchestration works by enforcing blocking user confirmation at key milestones. After generating a plan and verifying traceability to your design documents, the system halts to present the plan for your explicit approval before enabling downstream implementation steps.

The best way to ensure traceability between a work plan and design docs is through coordinated subagent verification. During the planning workflow, subagents generate the plan and actively verify that every planned item maps directly back to the original design document requirements.

No, you do not need to manually coordinate subagents to generate a plan. The system automatically spawns and manages subagents to handle plan creation, verify traceability to your design documents, and ensure readiness, requiring only your blocking approval at key milestones.