rpi-methodologylisted

# RPIV Methodology > Naming note: the skill directory is `rpi-methodology` (the historical short name); the methodology itself is RPIV — the V for Verify is a first-class phase, not an afterthought. ## Overview RPIV = **Research → Plan → Implement → Verify** Core principles: - **NEVER write code without an approved plan.** - **NEVER consider work done without verification.** ## Commands Chat-level command triggers — the user types these directly: | Command | Action | Wait for | | ------------------ | --------------------------- | ----------------- | | `research [topic]` | Investigation only, no code | — | | `plan [task]` | Research + create plan | `proceed` or `ok` | | `proceed` / `ok` | Execute approved plan | — | | `verify` | Run verification checklist | — | | `compress` | Compress context | — | | `status` | Show current state | — | ## Workflow ### 1. Research Phase ``` User: research how <library> handles <capability> Claude: - Reads documentation - Explores existing code - NO code modifications - Returns findings ``` ### 2. Plan Phase ``` User: plan add <capability> to <module> Claude: 1. Research (as above) 2. Create detailed plan: - Files to modify - Step-by-step changes - Potential risks 3. STOP and wait for approval ``` ### 3. Implement Phase ``` User: proce