work-unit-decomposition
SkillFiles & storageLets your agent break an implementation plan into small work units with checklists, file scopes, and dependencies.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the work-unit-decomposition skill
About this capability
Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.
What this skill tells your AI
The instructions your AI receives, as published by a5c-ai/babysitter in library/methodologies/metaswarm/skills/work-unit-decomposition/SKILL.md and read by ahel’s review.
- When decomposing a large feature into implementable chunks
- When preparing for orchestrated execution
Work Unit Structure
Each work unit specifies:
- ID - Unique identifier
- Title - Human-readable description
- Definition of Done - Enumerated checklist items
- File Scope - Which files the unit may modify
- Dependencies - Other work units this depends on
- Human Checkpoint - Whether human approval is needed before execution
- Parallel Safe - Whether it can execute alongside other units
Human Checkpoint Triggers
Mark human checkpoints for:
- Schema or database changes
- Security-sensitive code paths
- New architectural patterns not seen in codebase
- External API integrations
- Breaking changes to public interfaces
Agents Used
agents/architect/- Creates the decompositionagents/cto/- Validates TDD readiness per unit
Tool Use
Invoke as part of: methodologies/metaswarm/metaswarm-orchestrator (Phase 4)
Signals
- GitHub stars
- 2k
- Forks
- 106
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
work-unit-decomposition- Source
- github.com/a5c-ai/babysitter