From principled-implementation
Decompose a DDD plan into executable tasks with dependency ordering. Reads a plan file, extracts phases, bounded contexts, and individual tasks, then creates a task manifest for orchestration. Use when you have an active DDD plan ready for implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/principled-implementation:decomposeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Extract concrete, executable tasks from a DDD implementation plan and create a task manifest for orchestrated execution.
Extract concrete, executable tasks from a DDD implementation plan and create a task manifest for orchestrated execution.
/decompose <plan-path>
| Argument | Required | Description |
|---|---|---|
<plan-path> | Yes | Path to a DDD plan file (e.g., docs/plans/001-my-feature.md) |
Parse arguments. Extract <plan-path> from $ARGUMENTS.
Verify the plan. Read the plan file and confirm:
status is active (do not decompose complete or abandoned plans)Extract plan metadata. Run:
bash scripts/parse-plan.sh --file <plan-path> --metadata
Captures: title, number, originating_proposal.
Extract phases and tasks. Run:
bash scripts/parse-plan.sh --file <plan-path> --tasks
Outputs pipe-delimited structured data: phase number, task ID, description, dependencies, and bounded contexts per task.
Create .impl/ directory if it does not exist:
mkdir -p .impl
Initialize task manifest. Run:
bash scripts/task-manifest.sh --init \
--plan-path <plan-path> \
--plan-number <number> \
--plan-title "<title>"
Add each task to the manifest. For each extracted task:
bash scripts/task-manifest.sh --add-task \
--task-id <phase.task> \
--phase <phase-number> \
--description "<task description>" \
--depends-on "<comma-separated-phase-deps>" \
--bounded-contexts "<BC-N,BC-M>"
Report results. Display:
.impl/manifest.json/spawn <task-id> to execute a single task, or /orchestrate <plan-path> for automated execution."scripts/parse-plan.sh — Extract metadata and tasks from DDD plan markdown (canonical copy)scripts/task-manifest.sh — Initialize and populate task manifest (canonical copy)npx claudepluginhub alexnodeland/principled --plugin principled-implementationParses Markdown plan files from context/plans/ into Claude Code tasks with implementation, verification steps, and dependencies. Invoke via /implement-plan [filename] to create executable workflows.
Creates structured implementation plans for multi-step tasks from specs or requirements. Generates plan.json and task markdown files with explicit code and testing steps.