OpenParable
Skip to content
← Back to skills

Work Unit Decomposition

Productivity
work-unit-decomposition

Work Unit Decomposition is an Agent Skill for productivity published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/metaswarm/skills/work-unit-decomposition/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/work-unit-decomposition, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

  • 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)