02-planning

You can convert initial ideas into concrete product requirements by drafting PRDs, user stories, and scope documents using structured templates. Save the initial PRD to the .claude/02-planning/prd.md file to begin the planning workflow.

The best way to enforce planning governance is to apply a Plan, Review, Execute, and Re-verify cycle with explicit approvals. This ensures prerequisites are validated, artifacts are retained, and Phase 3 readiness is achieved before execution begins.

To structure and retain planning artifacts for traceability, scaffold files by creating execution plans and templates under the .claude/local/plans/<branch>/02-planning/ directory, ensuring all scope documents and PRDs are properly organized for review.

Yes, you need explicit approvals before executing a product scope plan to enforce governance. Securing approvals validates prerequisites, aligns the execution plan with KPIs, and confirms Phase 3 readiness before development proceeds.

You need to validate KPIs during the planning process to ensure Phase 3 readiness before execution. Aligning the PRD and scope documents with KPIs confirms that the execution plan meets governance prerequisites and product objectives.