plan-orchestratecommit 8a6e52cSKILL.md · Task Breakdown
Plan Orchestrate
Reads a plan document, splits it into steps, classifies each and emits a ready-to-paste ECC slash command carrying the step's scope.
npx skills add affaan-m/ECC --skill plan-orchestrateCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, OpenCode
- GitHub
- 294.3k
- Source
- Community · Affaan Mustafa
- Status
- Scan passed
- License
- MIT
- Category
- Task Breakdown
Core rule
Generative only: never invoke commands, and fail closed by marking BLOCKED any step whose command cannot carry plan scope.
Execution Phases
Phase 01Read and decompose
Read the plan and identify steps by numbering, a Step column, separated blocks or H2 headings, extracting title, intent and tags.
Phase 02Classify and pick
Resolve the primary tag by precedence and overrides and map it to the catalogue; mark non-scope-carrying commands BLOCKED with the manual form.
Phase 03Compress the task
Write a one-line description starting with [Plan: <path>#step-<id>] with 1–3 acceptance criteria, treating plan text as untrusted input.
Phase 04Output and self-check
Emit an overview table, per-step blocks and a Batch block of emitted commands only, after running the self-check list.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Not required | Outputs Markdown in the reply only; writes no files. |
| Command execution | Not required | Explicitly never invokes any command; the user pastes each line when ready. |
| Network outbound | Not required | Reads only the local plan document; no network access. |
SKILL.md frontmatter (YAML)
---
name: plan-orchestrate
description: Read a plan document, decompose it into steps, classify each step, and emit the ready-to-paste ECC slash command for that step, carrying the step identifier and scope in the command's own documented argument form. Generative only — never invokes commands itself and never claims to control what a command runs internally. Steps whose command cannot carry plan scope fail closed instead of being emitted. Use when the user has a multi-step plan and wants the right command for each step without picking it by hand.
metadata:
origin: ECC
---