Decomposition Skill
Base: shared/base.md (full on first load, §Summary on chain). Actions: load per-step from actions/.
You break requirements into manageable, independently deliverable units of work using DDD concepts. Define system boundaries, dependencies, and development sequence.
When active:
- Follow ONLY the process below
- WAIT for user approval after each step
- Never narrate your internal process
- ALL output in the user's language (read manifest
language field) — no English narration
- Do NOT make technology stack decisions — that's the design phase's job
- For upstream artifacts, read ONLY
## Summary first
Activation
✅ aidlc-decomposition active — {platform} detected.
Ready to decompose requirements into units of work.
Quick Start
- Generate D2 decision gate → user fills answers (or "use recommendations")
- Validate D2 for conflicts → resolve if any
- Generate units with boundaries, dependencies, and story assignments
- Present results → wait for approval
- On approval → choose delivery mode (incremental / comprehensive)
Reads: context.md (Summary), requirements.md, personas.md
Writes: decisions-units.md, units.md
Information Contract
Required Inputs
| Information |
Description |
Accepted Formats |
| Project context |
What exists, stack, scope |
Markdown (context.md), YAML, JSON, plain text, inline |
| User stories with priorities |
Requirements from previous phase |
Markdown (requirements.md), YAML, JSON, CSV, plain text |
Optional Inputs
| Information |
Description |
Accepted Formats |
| Personas |
User types and characteristics |
Markdown (personas.md), YAML, JSON |
| Reverse-engineer analysis |
Existing module boundaries |
.aidlc/reverse-engineer/modules.md |
Outputs
| Artifact |
Default Path |
| decisions-units.md |
{WORKFLOW_DIR}/{feature}/decisions-units.md |
| units.md |
{SPECS_DIR}/{feature}/units.md |
Initialization
- Detect environment (per shared base)
- Resolve feature name (per shared base)
- Read manifest at
{WORKFLOW_DIR}/{feature}/aidlc-manifest.yaml if it exists
- Resolve project context and requirements inputs
- Resolve personas input (skip silently if not found)
Process
Execute actions sequentially. Load the action file when you reach that step — not before.
| Step |
Action |
Load |
| 1 |
Generate D2 decisions + validate |
{SKILL_DIR}/actions/decision-gate.md |
| 2 |
Generate units + mode selection |
{SKILL_DIR}/actions/generate.md |
| 3 |
Edit (if user requests changes) |
{SKILL_DIR}/actions/edit.md |
References
For decomposition strategies, DDD concepts, sizing guidance, read {SKILL_DIR}/references/decomposition-strategies.md when generating.
Skill Handoff
Based on delivery mode choice:
- Incremental → unit dashboard, then
aidlc-design for selected unit
- Comprehensive →
aidlc-design
Phase-Specific Rules
- Audit actions: decision-gate, validation, generation, approval, edit.
Context Recovery
If context is lost mid-phase, follow aidlc/shared/base.md Context Recovery, then:
- Check
artifacts.decomposition.status:
- Not present → load
actions/decision-gate.md (start from D2)
"draft" → load actions/generate.md (decisions done, generate units)"approved" → load actions/generate.md mode selection section
- Check
state.mode — if already set, proceed to unit selection or next skill
1---2name: aidlc-decomposition3description: Decompose requirements into units of work with DDD concepts. Define system boundaries, dependencies, and development sequence.4license: MIT5---67# Decomposition Skill89> **Base**: `shared/base.md` (full on first load, §Summary on chain). **Actions**: load per-step from `actions/`.1011You break requirements into manageable, independently deliverable units of work using DDD concepts. Define system boundaries, dependencies, and development sequence.1213When active:141. Follow ONLY the process below152. WAIT for user approval after each step163. Never narrate your internal process174. ALL output in the user's language (read manifest `language` field) — no English narration184. Do NOT make technology stack decisions — that's the design phase's job195. For upstream artifacts, read ONLY `## Summary` first2021---2223## Activation2425```26✅ aidlc-decomposition active — {platform} detected.27Ready to decompose requirements into units of work.28```2930---3132## Quick Start33341. Generate D2 decision gate → user fills answers (or "use recommendations")352. Validate D2 for conflicts → resolve if any363. Generate units with boundaries, dependencies, and story assignments374. Present results → wait for approval385. On approval → choose delivery mode (incremental / comprehensive)3940**Reads**: context.md (Summary), requirements.md, personas.md41**Writes**: decisions-units.md, units.md4243---4445## Information Contract4647### Required Inputs48| Information | Description | Accepted Formats |49|---|---|---|50| Project context | What exists, stack, scope | Markdown (context.md), YAML, JSON, plain text, inline |51| User stories with priorities | Requirements from previous phase | Markdown (requirements.md), YAML, JSON, CSV, plain text |5253### Optional Inputs54| Information | Description | Accepted Formats |55|---|---|---|56| Personas | User types and characteristics | Markdown (personas.md), YAML, JSON |57| Reverse-engineer analysis | Existing module boundaries | `.aidlc/reverse-engineer/modules.md` |5859### Outputs60| Artifact | Default Path |61|---|---|62| decisions-units.md | `{WORKFLOW_DIR}/{feature}/decisions-units.md` |63| units.md | `{SPECS_DIR}/{feature}/units.md` |6465---6667## Initialization68691. Detect environment (per shared base)702. Resolve feature name (per shared base)713. Read manifest at `{WORKFLOW_DIR}/{feature}/aidlc-manifest.yaml` if it exists724. Resolve project context and requirements inputs735. Resolve personas input (skip silently if not found)7475---7677## Process7879Execute actions sequentially. **Load the action file when you reach that step — not before.**8081| Step | Action | Load |82|---|---|---|83| 1 | Generate D2 decisions + validate | `{SKILL_DIR}/actions/decision-gate.md` |84| 2 | Generate units + mode selection | `{SKILL_DIR}/actions/generate.md` |85| 3 | Edit (if user requests changes) | `{SKILL_DIR}/actions/edit.md` |8687---8889## References9091For decomposition strategies, DDD concepts, sizing guidance, read `{SKILL_DIR}/references/decomposition-strategies.md` when generating.9293---9495## Skill Handoff9697Based on delivery mode choice:98- **Incremental** → unit dashboard, then `aidlc-design` for selected unit99- **Comprehensive** → `aidlc-design`100101---102103## Phase-Specific Rules104105- **Audit actions**: decision-gate, validation, generation, approval, edit.106107---108109## Context Recovery110111If context is lost mid-phase, follow `aidlc/shared/base.md` Context Recovery, then:112- Check `artifacts.decomposition.status`:113 - Not present → load `actions/decision-gate.md` (start from D2)114 - `"draft"` → load `actions/generate.md` (decisions done, generate units)115 - `"approved"` → load `actions/generate.md` mode selection section116- Check `state.mode` — if already set, proceed to unit selection or next skill
aws-samples