work-unit-decomposition
Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.
npx skills add a5c-ai/babysitter --skill work-unit-decomposition --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- 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 decomposition - `agents/cto/` - Validates TDD readiness per unit ## Tool Use Invoke as part of: `methodologies/metaswarm/metaswarm-orchestrator` (Phase 4)
- Work Unit Structure
- Human Checkpoint Triggers
- Agents Used
- Tool Use
What does the work-unit-decomposition skill do?
Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill work-unit-decomposition --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.