Menu
Run the full Evoloop planning pipeline — start, area processing, review, red-team, and PM story generation — in sequence with progress tracking
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
Show planning area readiness status -- statuses, open questions, blockers, and next actions
Clone an existing Evoloop story as a template for a new one — copies structure, resets status, prompts for changes to title, requirements, and dependencies
Estimate the total prompt size that will be sent to an AI agent when processing an Evoloop story — warns if approaching model context limits
Visualize the Evoloop story dependency graph as text tree and Mermaid flowchart — shows critical path, blocked chains, and ready-to-run stories
Run Evoloop doctor checks and auto-fix common issues — missing directories, non-executable scripts, missing templates, and provide remediation for manual fixes
Deep-dive into a specific story's state — stage, failures, dependencies, last agent output, requirement verification, and suggested next action
| name | plan-all |
| description | Run the full Evoloop planning pipeline — start, area processing, review, red-team, and PM story generation — in sequence with progress tracking |
| disable-model-invocation | true |
| allowed-tools | ["Read","Glob","Grep","Bash","Edit"] |
Run all 5 subphases in order. Stop on any failure.
Parse $ARGUMENTS: --tool <tool> (default: claude), --max-area-iterations <N> (default: 5), --dry-run.
./scripts/doctor.sh --planning-only --skip-runner-tools. Fail → suggest /doctor-fix, stop../orchestrator.sh plan start --tool <tool>. Verify .plan/areas.md exists after..plan/areas.md table. For each non-approved/locked area, run ./orchestrator.sh plan area --area <name> --tool <tool>. Re-read status after each; retry up to max iterations. If area doesn't reach approved → report and stop../orchestrator.sh plan review --tool <tool>./orchestrator.sh plan redteam --tool <tool>./orchestrator.sh plan pm --tool <tool>./scripts/doctor.sh (full). Pass → show counts, suggest ./orchestrator.sh run. Fail → suggest /validate.Run preflight only, show areas that would be processed, print command sequence, note already-approved areas.
Show full output, identify failed step (e.g., "Failed at Step 3/6: Area Processing (area: backend)"), suggest manual retry command. Re-running /plan-all skips already-approved areas.