plan-orchestrator
SolidRoute hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb table, intent classifier, and 3-stage routing pipeline.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- nguyenthienthanh
- Repository
- nguyenthienthanh/aura-frog
- Created
- 9 months ago
- Last Updated
- 1 weeks ago
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
plan
Activate the heavy planner→/orchestrate chain — write a structured plan file with Agent Dispatch Manifest, then invoke the /orchestrate skill to execute it in waves. Reserve for genuinely multi-file / multi-hour / multi-agent work (large refactors, migrations, features spanning many files). For single-session-sized work (one or a few files), use built-in plan mode (shift-tab) instead — not this skill.
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".
plan-loader
Loads minimum hierarchical plan context (.claude/plans/) for current execution focus. Auto-invokes every session when plans exist. Stays under 800 always-loaded tokens regardless of plan tree size.