From sdd
Decomposes specification documents into independent changes using outline, section, or hierarchical modes with dependency graphs and independence scores.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdd:spec-decompositionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a specification document to identify natural change boundaries and return a structured decomposition result. This is a pure analysis skill that takes input and returns output without user interaction.
Analyze a specification document to identify natural change boundaries and return a structured decomposition result. This is a pure analysis skill that takes input and returns output without user interaction.
Schema: schemas/input.schema.json
Accepts decomposition mode, spec content, and mode-specific parameters for outline, section, or hierarchical decomposition.
Schema: schemas/output.schema.json
Returns mode-specific results: outline sections, or hierarchical epic/feature groupings with dependency graph.
For detailed guidance, read these on-demand:
Modes: outline (extract headers), section (analyze one section), hierarchical (epics + features), default (full analysis)
Algorithm phases: Structure Extraction -> Boundary Detection -> Dependency Detection -> Independence Scoring -> Refinement
Complexity levels: SMALL (<= 3 ACs), MEDIUM (4-8 ACs), LARGE (> 8 ACs), EPIC (> 10 ACs + 3+ components)
Independence score: 0.0-1.0 scale; >= 0.5 is standalone, < 0.3 should be merged
npx claudepluginhub liorcohen/sdd --plugin sddConvert technical designs into actionable, tracked task hierarchies with sizing, dependencies, and acceptance criteria. Invoke whenever task involves any interaction with work decomposition — breaking down features into subtasks, slicing work items, creating task lists, or writing decomposition documents.
Decomposes a unified docs/specs artifact into granular, parallelizable tasks with internal traceability to DR-N requirements. Applies a verification ladder matching test depth to blast radius.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.