| name | workflow-atomic-decomposition |
| description | Use when a revised spec is ready to split into selected workflow slices, atomic implementation items, bootstrap prerequisites, dependency edges, verification loops, and traceable work items. |
Workflow Atomic Decomposition
Purpose
Split a revised spec into implementation-sized atomic items that can be independently executed, tested, reviewed, committed, and advanced through the spec-driven workflow.
Script-First Execution
Read the revised spec and the Devil's Advocate gate result directly from their artifacts. When a durable orchestrator state artifact exists as JSON, validate it first:
python agent-skills/orchestrator-state-machine/scripts/validate_orchestrator_state.py path/to/state.json --json
Run the helper from Windows PowerShell or a POSIX shell (Linux/macOS) with the same command shape; use python3 when python is unavailable.
Use LLM judgement only for slicing, dependency edges, and item design.
Prompt Contract
Stable prefix:
- Skill:
workflow-atomic-decomposition
- Execution Profile:
heavy-llm
- Reusable Rules: atomic items describe verifiable behavior or contracts, not just file lists; each item must be small enough to implement, test, review, and commit alone; dependency edges must be explicit; replacement, migration, and compatibility work become explicit items when behavior changes.
- Scope / Governance Defaults: no implementation of items here; do not turn future ideas into accepted work without human approval; do not rely on chat order as dependency metadata.
- Output Contract: see the
### Workflow Atomic Decomposition Report template under ## Output.
Dynamic run packet:
- User Request:
- Deterministic Evidence:
- Relevant Files Or Artifacts:
- Current Assumptions Or Gaps:
- Requested Judgement Or Transformation:
Workflow
- Read the revised spec, accepted scope, non-goals, Devil's Advocate gate result, and open questions.
- Confirm the gate is
pass; if not, stop and report blockers.
- Identify main workflow candidates and ask for or infer the selected workflow when safe.
- Identify candidate workflow slices, then split the selected workflow into atomic items based on behavior, contract, validation boundary, and dependency edges.
- Add bootstrap prerequisite items such as
P0-00 when scaffolding is required before behavior work.
- Include replacement, compatibility, and migration items when the spec changes existing behavior.
- For each item, define ID, title, status, spec refs, allowed scope, forbidden scope, dependencies, validation, mutation expectation, and completion criteria.
- Classify decomposition gaps and state whether the workflow can continue or must return to spec clarification.
- Keep backlog, deferred, proposed, and accepted items separate.
- Hand off item metadata to
orchestrator-state-machine.
Mandatory Rules
- Atomic items describe verifiable behavior or contracts, not just file lists.
- One item should be small enough to implement, test, review, and commit alone.
- Dependency edges must be explicit.
- Every item needs spec refs and validation hooks.
- Replacement, migration, and compatibility work must become explicit items when behavior changes.
- Do not enter implementation while decomposition blockers remain.
Boundaries
- Do not implement the items in this skill.
- Do not turn future ideas into accepted work without human approval.
- Do not rely on chat order as dependency metadata.
Validation
Check:
- Selected workflow is clear.
- Every atomic item has spec refs.
- Dependencies are explicit.
- Validation is defined.
- Open questions or gaps are listed.
- Gap/no-gap continuation decision is explicit.
- Items can support commit-then-advance.
Output
Use this report template:
### Workflow Atomic Decomposition Report
| ID | Title | Status | Spec Refs | Dependencies | Validation | Completion Criteria |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
- Main workflow map:
- Candidate workflow slices:
- Selected workflow:
- Dependency graph:
- Bootstrap prerequisite items:
- Replacement, compatibility, or migration items:
- Deferred items:
- Gap classification:
- Gap/no-gap continuation decision:
- Next orchestrator state patch:
