story-to-plan

Converting an INVEST story into an executable vertical plan involves loading governance context such as ADRs, API contracts, and CLAUDE.md. The story is then decomposed into vertical slices (DB/BE/FE/Tests) with explicit consume and produce declarations to create a standard plan file.

Story decomposition handles architectural governance by loading ADRs, API contracts, and CLAUDE.md to ensure generated plans align with existing constraints. This governance context dictates the structure of the vertical slices and their stable namespace declarations.

Yes, you can generate vertical slice plans for both greenfield and brownfield stories. The approach decomposes stories into vertical slices across DB, BE, FE, and Tests while applying the loaded governance context to fit the specific project environment.

The standard output file format for vertical slice planning is a markdown file named plan-H<N>.md. This file is generated in the docs/06-plans/ directory and contains the structured vertical slices ready for dependency analysis.

Yes, the generated plan-H<N>.md file is designed to be consumed by a task-dependency-analyzer. The analyzer uses the file's structured vertical slices and consume/produce declarations to build a DAG and execute the plan.

A limitation of using vertical slices with stable namespaces is that it requires pre-existing governance context like ADRs and API contracts to function correctly. Without these governance files, the generated plan may not align with your project's architectural constraints.