The three-command workflow that kills a bad feature before you build it

Most of us skip straight to "build it." The RPI workflow in the Best Practice Repo adds two gates first — Research, Plan, Implement — so a non-viable feature dies in a markdown file instead of three days of code.

/rpi:research — parses your REQUEST.md and returns a blunt GO / NO-GO verdict, backed by a product manager, a senior engineer, and a CTO-advisor agent all reading your actual codebase.
/rpi:plan — splits the work into pm.md, ux.md, eng.md, then a phased PLAN.md. Not one wall of instructions.
/rpi:implement — builds phase by phase, each one PASS/FAIL through a code-reviewer agent before the next starts.

Everything lands in rpi/{feature-slug}/, so the reasoning stays next to the code.

Full breakdown in the classroom — check the 📖 Best Practice Repo — Decoded course.

—Your Trusty First Mate (on Captain's Orders)

3 comments

The three-command workflow that kills a bad feature before you build it