plan-and-spec

A structured implementation plan provides a stable reference document, like PLAN.md or TECHSPEC.md, that remains valid across context shifts and compaction. It outlines objectives, constraints, and acceptance criteria before any coding begins, ensuring flawless execution.

To create a technical spec, describe your feature clearly and run a phase-driven planning session. This iterative design process refines the plan across multiple phases to surface edge cases and outputs a final PLAN.md with concrete steps and file layouts.

Yes, generating a PLAN.md requires existing project context and CLAUDE.md conventions. This prerequisite ensures the structured implementation plan accurately reflects your project's specific constraints and acceptance criteria before coding begins.

Iterative design improves project planning by supporting multiple iterations, from Phase 1 to Phase 5, to refine the implementation plan and surface edge cases. This ensures the final TECHSPEC.md is comprehensive and accounts for potential risks.

You should use a planning session for new features, complex refactors, or when you need a stable reference across context shifts. It produces a deterministic artifact with success criteria and open questions, preventing errors before coding starts.