vibe-plan
Planning Work
One pass from a request or a loose idea to agent-grabbable tickets. Four stages: triage (judge an incoming external request; may end the run), grill (sharpen by interview, writing docs as decisions land), spec (synthesise what was decided), tickets (split into tracer-bullet slices with blocking edges).
The issue tracker and triage label vocabulary should have been provided to you — run /vibe-init if not.
Enter at the right stage
Ask nothing you can infer from what the user brought. Read the argument and the conversation, then enter at the first stage whose input you don't already have:
| What the user brought | Enter at |
|---|---|
| An external request — a bug report, feature request, issue link or number you didn't write, or an external PR | Stage 0 — Triage |
| A loose idea, or a plan with open questions | Stage 1 — Grill |
| A settled conversation, no open decisions | Stage 2 — Spec |
| An existing spec, PRD, plan, issue number, or URL you authored | Stage 3 — Tickets |
Treat it as external when the origin isn't you. A bare link or issue number, a pasted report, "someone filed…", a contributor's PR — anything whose content you and the user didn't produce in this repo's planning goes through Stage 0 first. Tickets this skill published are already ready-for-agent by construction: never triage your own output. If it's ambiguous, say which way you read it and let the user correct you in a word.