joycraft-decompose

To decompose a feature brief into atomic testable specs, provide the feature objective to generate a structured 3-7 spec breakdown. This breakdown includes per-spec naming, dependency tracking, and docs/specs entries to support repeatable execution.

Spec-driven decomposition for feature planning is the process of breaking down a feature brief into small, independently executable specs. It enables precise planning and reliable implementation by generating a structured spec breakdown with dependency tracking.

Yes, you can use inline descriptions for feature decomposition instead of full docs. The decomposition process accepts briefs sourced from docs/briefs, inline descriptions, or standalone requests, producing a structured 3-7 spec breakdown.

During the feature breakdown process, a 3-7 spec breakdown is generated. Each atomic spec includes specific naming conventions, dependency tracking, and generates docs/specs entries to support repeatable execution.

The best way to track dependencies when breaking down features into specs is to use structured decomposition. This approach enforces per-spec dependency tracking within a structured table and generates docs/specs entries for repeatable execution.