raplisted
Install: claude install-skill wkhori/rap
# rap — Research And Plan
Turn a brief into one plan an agent can execute end-to-end. Fit the effort to the job: a small change gets a one-page plan in minutes; a new system gets parallel research, a Challenger, and a full plan. Never the reverse — long sessions that produce mediocre plans are the failure mode this skill exists to prevent.
Brief: `$ARGUMENTS`. If empty, ask exactly one intake question ("What are we building or changing — and is there a brief, rubric, or deadline I should read?") and never ask another intake question. A ticket key (Jira, Linear, GitHub issue) counts as a brief: fetch the ticket and treat its text as the brief. A `--quick|--standard|--deep` flag forces the tier.
## 1. Triage (lead, inline)
Read the brief in full (if it is a path, read the file). Orient in the repo: `CLAUDE.md`, `AGENTS.md`, `README`, one glob pass, where docs/plans already live. If the user supplied a research or design doc, treat it as settled — extend it, don't redo it.
Decide three things and state them in chat in ≤3 lines before continuing:
- **Mode** — `greenfield` (new repo) · `feature` (existing repo, additive) · `revision` (changing existing design/behavior). Mode is not size: a greenfield 1-file tool is S.
- **Size** — by scope signals, never by time. When signals straddle bands, take the larger.
- **S** one file or one concept; no new deps; no schema change
- **M** a handful of files in one subsystem; ≤1 new concept; ≤1 new dep
- **L** crosses 2+ subsystem