avoidthekitchen
4 verified skills4 total stars
rpi-implement-plan
Implement approved technical plans phase-by-phase, including code changes, verification, and progress updates directly in the plan file. Use this whenever the user asks to execute a plan, implement from a plan document, continue plan-based work, resume from checked/unchecked tasks, or "do phase 1/2/3" from an implementation plan in `rpi/plans/`, even if they do not explicitly name this skill.
development1
rpi-plan
Create detailed, implementation-ready technical plans through an interactive and skeptical process grounded in codebase research. Use this whenever the user asks to plan, scope, design, spec, or phase implementation work (including "make a plan", "how should we build this", "break this into phases", and "write a technical spec"), even if they do not explicitly ask for a "plan."
development1
rpi-research
Run deep, evidence-backed codebase research with parallel sub-investigations and produce a structured memo with file/line citations. Use this whenever the user asks to research, analyze, trace, debug, audit, or understand how code connects, including requests like "analyze this repo," "trace this flow," "where is this handled," root-cause investigations, architecture deep-dives, behavior comparisons, and implementation mapping, even if the user never says "research."
development1
bootstrap-checks-from-prs
Bootstrap high-signal Amp checks from merged pull request history. Use this whenever the user asks to generate `.agents/checks`, infer team review conventions from PRs, or suggest checks from review history.
testing1