Help us improve
Share bugs, ideas, or general feedback.
From planr
Routes user requests to the correct Planr skill based on project state. Use when the user hasn't named a specific skill.
npx claudepluginhub instructa/planr --plugin planrHow this skill is triggered — by the user, by Claude, or both
Slash command
/planr:planrThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the dispatcher. Do not improvise workflow prompts; route to one Planr skill and follow it exactly. Skills are the prompts.
Plans tasks or features: loads project context including monorepo checks, clarifies requirements, spawns Plan agent, persists validated plans to .groundwork-plans/.
Manages task planning and Plans.md tracking with create, add, update, sync subcommands. Useful for structured plan creation and progress sync.
Coordinates coding agents with a live task graph using Planr. Handles project planning, dependency linking, item picking, review gates, and interruption recovery.
Share bugs, ideas, or general feedback.
You are the dispatcher. Do not improvise workflow prompts; route to one Planr skill and follow it exactly. Skills are the prompts.
Routing is decided by live state, not by guessing:
planr project show --json
planr map show --json
planr review list --open
planr approval list --open
If no project exists, initialize before anything else:
planr project init "Project Name" --client all
Initialization happens once per repository. If a project already exists, never re-init: new features, refactors, and fixes get their own feature-scoped plan (planr plan new "Feature"), and planr map build --from <build-plan-id> extends the existing map with new linked items.
Evaluate top to bottom; pick the first row that matches both intent and state:
| Intent | State condition | Route |
|---|---|---|
| "build until done", "loop", "finish this feature autonomously" | any | planr-loop |
| status, "what's left", "what's blocked" | any | planr-status |
| summary of completed scope | any | planr-summary |
| new idea, PRD, scope, architecture | no plan, or plan needs refinement | planr-plan |
| new feature, refactor, or fix on an existing project | project exists, scope has no plan yet | planr-plan (feature-scoped plan, then extend the map) |
| plan exists but no map / map needs structure, dependencies, breakdown | build plan checked, map missing or stale | planr-task-graph |
| review requested or open review exists | open review on the map | planr-review |
| implement, fix, continue work | ready items exist on the map | planr-work |
| implement, but nothing is ready | all items blocked | planr-status, then report blockers to the user |
planr-loop and let the loop sequence the stages.Use $planr-work on item <id>), never with a hand-written workflow prompt.planr-review in a separate agent or subagent whenever the host supports it.