plot

Systematically interrogate implementation plans through adaptive depth interviews covering technical, domain, UX, and non-functional dimensions to uncover gaps and validate decisions. Use when: user wants to challenge, refine, or validate a plan, spec, or idea. Triggers: challenge the plan, challenge me, quiz me, interview me, refine plan, validate plan, review plan, interrogate plan, stress-test plan, challenge the spec, challenge the story, review spec, review story.

Git-native planning dispatcher. Analyzes current git state and suggests the next action. Activates on /plot or when managing planned work through git branches and PRs. Spoke commands: /plot-idea, /plot-approve, /plot-deliver, /plot-reject, /plot-reconcile, /plot-release, /plot-sprint.

Record a plan's approval through its declared review channel (merge the plan PR, record an in-session go, or tally a ballot) and stop — implementation starts separately with /plot-implement. Part of the Plot workflow. Use on /plot-approve.

Set the Plot board up in a project that already has Plot: probe the prerequisites, record the git-host and CI configuration, then start the board and prove it serves. Use on /plot-board-setup.

Verify all implementation is done, then deliver the plan. Part of the Plot workflow. Use on /plot-deliver.

Fan out an approved plan's eligible branches: one git worktree and one detached worker per branch, each claimed atomically. The writing half of the fleet. Use on /plot-dispatch.

Fleet pulse — report which branch waves of a plan are complete, eligible, blocked or unapproved, and which branches are claimed. Stateless — every fact is re-derived from git; the only thing written is a pulse line. Use on /plot-fleet.

Create a plan with ceremony matched to the change: answer the two ceremony questions (review channel, implementation home) within the repo's declared bounds, then create the plan file — on an idea branch with a draft PR, on the work branch, or directly on the default branch. Part of the Plot workflow. Use on /plot-idea.

Start (or resume) implementation of an approved plan: staleness preflight, branch setup per the plan's recorded ceremony answers, a hand-off brief that pre-answers the mechanics, and a Started record. Prepares and records — never implements. Part of the Plot workflow. Use on /plot-implement.

Adopt Plot in a repository: probe what the repo already is, propose the Plot Config from that, create the plan/story skeleton, and offer optional extensions only where the repo shows it needs them. Use on /plot-init.

Compute a safe merge order for a plan's finished branches and predict which will collide, without merging anything. Use on /plot-merge-queue.

Plot/branch hygiene sweep — enumerate plan phase↔symlink drift, merged-but-not-delivered plans, and stale branches. Read-only; prints remediating commands, the human decides what to run. Use on /plot-reconcile.

Reverse a premature delivery — move plan from Delivered back to Approved. Part of the Plot workflow. Use on /plot-reject.

Verify release readiness and guide the release process. Part of the Plot workflow. Use on /plot-release.

Repair a plan whose wave holds several branches: read the entangled branches — their diffs, PRs and conflicts — propose one named wave per branch in an argued dependency order, confirm the order with a person, then rewrite only that plan's `## Branches` section. Proposes; a person confirms. Part of the Plot workflow. Use on /plot-reslice.

Manage time-boxed sprints with MoSCoW prioritization. Part of the Plot workflow. Use on /plot-sprint.

Only activate on explicit /ralph-plot-sprint invocation — never auto-activate. Use when ralph-sprint.sh drives a sprint iteration, or when manually debugging a specific sprint iteration by slug.

Use when user says "continue on", "work on", "create story", "new story", "resume", or references a JIRA ticket for multi-session work. NOT for Storybook UI component stories.

Use when facing technical uncertainty, unproven architecture, or building a large feature where agents or humans risk getting lost in details before confirming the architecture works. Prevents horizontal layer-by-layer building that delays integration feedback.