Menu
Transforms an approved enriched roadmap into an orchestration plan. Use when creating an orchestration plan, producing a build plan, or resuming a project from a saved plan. Not for roadmap creation/enrichment or workflow tier selection.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Delegates a task to OpenAI Codex running as an interactive session in a herdr pane - uses the user's ChatGPT subscription, visible in herdr, steerable mid-session. Use when delegating work to codex, offloading a task to a GPT model (sol, terra, luna), or running a second opinion from a non-Claude frontier model. Not for Claude Code's own Agent tool or local-LLM delegation (delegating-to-local-llm).
Delegates a task to a local LLM running as a Pi coding-agent session in a herdr pane - the subagent is visible in herdr, can be steered mid-session, and costs no cloud tokens. Use when delegating work to a local model, spawning a Pi subagent, offloading a task to omlx (qwen, gemma), or running agent work offline. Not for Claude Code's own Agent tool or subagents inside Pi.
Loads the rageatc-code-oss operating rules directly from the plugin when the SessionStart hook has not delivered them. Use when the rageatc-code-oss failsafe line appears in session-start hook output, when the plugin's operating rules are absent from context, or when the injected rules look truncated.
Loads the rageatc-core-oss operating rules directly from the plugin when the SessionStart hook has not delivered them. Use when the rageatc-core-oss failsafe line appears in session-start hook output, when the plugin's operating rules are absent from context, or when the injected rules look truncated.
Raises an artefact's signal-to-noise ratio by removing text that earns nothing for its reader โ filler, repetition, over-explanation, ornamental phrasing โ and relocating conditional detail to references. Use to slim a skill, agent, or document, cut bloat, tighten prose, or shrink a file that has grown too long. Tuned for SKILL.md files.
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed โ whether creating from scratch or extracting patterns from existing code.
| name | planning-software |
| description | Transforms an approved enriched roadmap into an orchestration plan. Use when creating an orchestration plan, producing a build plan, or resuming a project from a saved plan. Not for roadmap creation/enrichment or workflow tier selection. |
Produces an orchestration plan from an approved enriched roadmap. The plan is the orchestrator's execution contract โ it records the workflow tier, tracks chunk progress, and holds everything project-specific a fresh session needs to resume; the execution protocol itself lives in orchestrating-software-dev, which any resuming session loads.
The plan describes process (agent sequence, review perspectives, gates); the roadmap describes content (what to build in each chunk). Separate documents, separate owners โ never duplicate roadmap content into the plan.
Inputs (request anything missing before proceeding): approved enriched ROADMAP.md; workflow tier (decided upstream by orchestrating-software-dev); project name; confirmation that PRD.md and ARCHITECTURE.md exist (referenced, not duplicated).
Outputs: ORCHESTRATION-PLAN.md (the workflow contract) and an empty append-only ORCHESTRATION-LOG.md, both in the project root.
Not covered: roadmap creation/enrichment, tier selection, the per-chunk execution protocol and log entry format (both defined in orchestrating-software-dev).
Read ROADMAP.md completely. Note: total chunk count and IDs; phased (Thorough) or flat; parallel dispatch annotations; any chunk already in-progress.
| Tier | Plan depth |
|---|---|
| Quick | Short โ no phases section, flat chunk list, no whole-project review step |
| Standard | Full โ sequential chunks, whole-project review at end |
| Thorough | Full with phases โ phase groupings, parallel dispatch annotations, whole-project review at end |
Populate the Template below:
[ ] not started, [~] in-progress, [x] complete.Create it with a header comment only โ the entry format lives in orchestrating-software-dev:
# Orchestration Log
<!-- Append-only. Do not edit previous entries. -->
Adapt to the workflow tier per the annotations.
# Orchestration Plan โ [Project Name]
**Tier:** [Quick / Standard / Thorough]
**Created:** [YYYY-MM-DD]
**Roadmap:** ROADMAP.md
**PRD:** PRD.md
**Architecture:** ARCHITECTURE.md
---
## Upstream Steps
- [x] PRD โ PRD.md
- [x] Architecture โ ARCHITECTURE.md
[Standard/Thorough add:]
- [x] Interface Design โ .interface-design/system.md (if project has UI)
- [x] Decomposition โ ROADMAP.md (structure)
- [x] Enrichment โ ROADMAP.md (executable)
---
## Build Progress
<!-- Update status markers as work proceeds: [ ] not started, [~] in-progress, [x] complete -->
- [ ] chunk-001: [name]
- [ ] chunk-002: [name]
[... repeat for all chunks ...]
[Standard/Thorough add:]
- [ ] Whole-project review
---
## Execution
For each chunk, in dependency order, run the Per-Chunk Execution Protocol from the orchestrating-software-dev skill.
**Review perspectives (resolved for this tier):**
[Quick:]
- spec-compliance
[Standard:]
- spec-compliance โ code-quality โ design-compliance (if system.md exists and chunk touches UI)
[Thorough:]
- spec-compliance โ code-quality โ design-compliance (if system.md exists and chunk touches UI) โ security (if chunk handles user input or sensitive data)
---
## Completion
[Quick: omit this section]
[Standard/Thorough:]
After all chunks are marked complete, run Stage 9 (Completion Review โ whole-project review, then user emulation) from the orchestrating-software-dev skill.
---
## Resumption Note
New session? Read this file. Find the first `[~]` or `[ ]` chunk in Build Progress. Resume from there using the Per-Chunk Execution Protocol from orchestrating-software-dev.
Resuming mid-chunk: for a [~] chunk, check ORCHESTRATION-LOG.md for the last completed step, re-read the chunk from ROADMAP.md, and resume where the developer-agent left off.
Tier change after plan creation: do not modify an existing plan's tier mid-project. If scope expands significantly, note it in ORCHESTRATION-LOG.md and create a revised plan.
Parallel chunks (Thorough only): note parallelisable chunks in Build Progress (e.g., - [ ] chunk-003: [name] [parallel with chunk-004]); dispatch concurrently when file sets do not conflict.
Quick tier with security concern: override the spec-compliance-only default โ load the security perspective for any chunk handling authentication, user input, or sensitive data.