make-groups

To break down a large feature specification, you can decompose the document into sequenced implementation groups. This process clusters requirements, establishes inter-group dependencies, and outputs structured files for incremental development pipelines.

Sequencing implementation groups requires analyzing requirement dependencies within architecture proposals. The decomposition process identifies interdependencies, clusters requirements into logical units, and orders the output groups to ensure a logical development flow.

Yes, decomposed requirement groups are formatted for pipeline consumption. The process generates an index file, per-group files, and a machine-readable manifest, ensuring the structured output integrates seamlessly with incremental development pipelines.

To verify decomposed requirement groups against an existing codebase, the decomposition process utilizes subagents. These subagents perform codebase verification during the requirement clustering and sequencing phases to ensure alignment.

Yes, requirement decomposition works for architecture proposals and product specs. The process analyzes extensive documents, identifies logical chunks of work like core data models, and structures them into ordered implementation groups.

When decomposing a 50-page product requirements document, the process relies on strict output formatting and subagent verification. Limitations depend on the source document's clarity, as ambiguous requirements may affect the accuracy of generated implementation groups.