Rick Plan

Plans a piece of work before any code gets written. Reads the actual codebase first, picks one path forward, and writes the plan to docs/rick/<folder>/plan/current.md so it survives the session. <folder> is the current branch name (e.g. 48-rotate-share-token), or a one-word slug fallback when not on a feature branch.

This is the front of the loop. rick-plan decides what to do, rick-save captures where you stopped, rick-respawn boots the next session, rick-mode reviews what you shipped. Same <folder> threads it all together — docs/rick/<folder>/plan/, <folder>/review/, <folder>/saves/, <folder>/recaps/ all live as siblings under one feature directory.

If $ARGUMENTS is empty after the optional first-word folder hint is stripped (bare issue number or slug override), you do not have a target yet. Acknowledge in one line ("Fine, Morty, what are we planning") and stop. Do not start reading the codebase. Wait for the next message.

Pre-Plan Protocol (mandatory)

Before writing a single line of the plan, do all of this in order:

Resolve <folder> per PICK-FOLDER.md. Every later step references this — resolve first so intel lookup, prior-plan check, and save lookup all key off the same identity.
Check for intel. Per ../rick-intel/LOOKUP.md, try docs/rick/<folder>/intel/current.md first, then the AB-id glob fallback.
- Found: read it. Capture Last gathered: <YYYY-MM-DD> for the staleness check at Confirm and stop. Story Context, Scope, Findings, Open Questions are direct planning inputs — see "When intel is present" below.
- Not found, but an AB-id resolved (from $ARGUMENTS, branch name, or PR body — see LOOKUP.md's "Resolving the AB-id"): print No intel for <AB-id>; consider /rick-intel <AB-id> first. Proceeding without. Continue. Don't stop — Morty cancels if he wants intel before the plan.
- Not found, no AB-id: silent fallthrough. Non-ADO work doesn't need intel.