impl-plan

To create an implementation plan, you transform a requirements document into a structured breakdown with problem framing, requirements traceability, and unit decomposition. This grounds your feature build in existing repo conventions and prior research.

Requirements traceability in implementation planning maps each verifiable task back to specific source requirements. This ensures your structured plan covers all requested features and clarifies the rationale for every codebase change.

Structure your implementation plan by researching prior learnings and performing targeted codebase exploration. This grounds the unit decomposition in established repo conventions, test patterns, and runtime verification expectations.

Implementation planning requires reading a source requirements document, such as spike findings or deliberation outcomes. The source path input is used to research prior learnings and emit a dated markdown plan.

The best way to include plan hardening signals is to explicitly mark required versus present or absent conditions. This ensures your implementation plan passes review gates by defining runtime verification and closure expectations for changed surfaces.

Decompose a feature requirement by applying structured implementation planning that breaks down the source document into verifiable tasks. This process includes problem framing and unit decomposition for downstream stage execution.