writing-plans

Turn a software spec into an implementation plan by decomposing requirements into actionable tasks with explicit file touchpoints, testing steps, and documentation requirements. This provides a clear end-to-end roadmap for engineers to follow.

Document file touchpoints and testing steps by generating a comprehensive implementation plan that maps out exactly which files to modify, what code to write, and how to verify results using TDD and DRY principles.

Yes, this implementation plan approach is best-suited for onboarding new engineers, scoping features from vague specs, and aligning multiple teams on a plan by ensuring zero-context handoffs and reducing guesswork across initiatives.

Yes, the generated implementation plan includes guidance for commits, versioning, and iterative delivery by enforcing TDD and DRY principles throughout the development lifecycle of the feature.

Structure an implementation plan using YAML frontmatter with name and description fields, followed by a Markdown body with required section headers, a single-line Quick Start, and metadata fields including complexity, category, keywords, dependencies, and components.