← ClaudeAtlas

masterplanlisted

Use when the user invokes masterplan as a normal Codex chat request, $masterplan, /masterplan, /masterplan:masterplan, asks to brainstorm, plan, execute, resume, import, doctor, status, next, retro, or clean masterplan work, or asks about existing docs/masterplan run bundles created by Claude.
rasatpetabit/masterplan · ★ 7 · AI & Automation · score 73
Install: claude install-skill rasatpetabit/masterplan
# Codex entrypoint for Superpowers Masterplan This skill is the Codex-visible entrypoint for Superpowers Masterplan. Its job is to load the canonical command prompt and adapt it to the current Codex runtime. ## Source of truth (v5.0 lazy-load layout) As of v5.0, `commands/masterplan.md` is a thin router (≤20 KB; enforced by doctor check #36). Per-phase behavior lives in `parts/step-{0,a,b,c}.md`, doctor lives in `parts/doctor.md`, import lives in `parts/import.md`, and cross-cutting contracts live under `parts/contracts/`. Codex-hosted runs should load the router first, then load only the phase file the router dispatches to. Do not pre-read all phase files. Resolve the router and phase files in this order: 1. `../../commands/masterplan.md` and `../../parts/` relative to this `SKILL.md` file. 2. `$PWD/commands/masterplan.md` and `$PWD/parts/` when running inside the plugin repo. 3. `/path/to/masterplan/commands/masterplan.md` (+ sibling `parts/`). 4. `$HOME/.codex/.tmp/marketplaces/rasatpetabit-masterplan/commands/masterplan.md` (+ sibling `parts/`). 5. `$HOME/.claude/plugins/marketplaces/rasatpetabit-masterplan/commands/masterplan.md` (+ sibling `parts/`). 6. `$HOME/.claude/commands/masterplan.md`. If none exists, say the local masterplan command file is missing and stop before inventing behavior. For ordinary runtime invocations, load the router (`commands/masterplan.md`) and dispatch by verb to the right phase file: - Bare `/masterplan` and `status` / `next`: router