Decompose large documents into sequenced implementation groups with dependency metadata.
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill make-groups
Please help me install this Agent Skill. Skill: make-groups Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/make-groups Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill make-groups
This Skill tackles the complexity of large projects by breaking down extensive documents, like feature specifications or architecture proposals, into smaller, manageable, and sequentially executable implementation groups.
make-plan pipeline.Use the make-groups skill to decompose the requirements in the attached document 'feature-spec-v2.md' into sequenced implementation groups.
High-intent search queries and answers about installing and using this skill.
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.
CodenburgGenerate technical design documents from proposals and specifications.
TrecekBreak large documents into sequenced implementation groups with explicit dependencies.
marcellourbaniGuide ABAP solution development from requirement validation through Clean ABAP code writing.
GabeujinGenerate and update machine-readable implementation plans with phases and atomic tasks.