菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.
Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.
| name | decompose |
| description | 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. |
| allowed-tools | Read, Write, Bash(ls *), Bash(grep *), Bash(find *), Bash(mkdir *), Bash(bash plugins/*) |
| user-invocable | true |
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)