
Qrspiv
- 4 repo stars
- Updated April 11, 2026
- rafadorado/qrspiv
QRSPIV is a Claude Code plugin that structures feature development into seven context-isolated phases so developers can align on design before implementation.
About
QRSPIV is a Claude Code plugin that evolves HumanLayer's RPI methodology into seven focused phases: Question, Research, Design, Outline, Plan, Implement, and Validate. Each slash command stays under 40 instructions, research runs without implementation bias, and humans approve design before code. Use it when monolithic agent prompts produce unreadable plans or polluted research. Every work item yields a tracked thoughts/ folder with questions, research, design, outline, plan, and validation artifacts.
- Seven focused commands under 40 instructions each
- Context-isolated research hides implementation goals
- Produces thoughts/ artifact folders per work item
- Adds validation gate before commit
Qrspiv by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add rafadorado/qrspivAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 4 |
|---|---|
| Last updated | April 11, 2026 |
| Repository | rafadorado/qrspiv ↗ |
How do I keep coding agents from producing bloated plans, biased research, and unreviewable implementation dumps?
Run a seven-phase QRSPIV workflow from research questions through design, plan, implement, and validate gates.
Who is it for?
Developers shipping non-trivial features who want HumanLayer-style phased alignment with explicit human gates and artifact traceability.
Skip if: One-line bug fixes or tasks where a single prompt-and-implement pass is sufficient.
What you get
Creates a thoughts/<work-id>/ folder with task, questions, research, design, outline, plan, and validation markdown artifacts.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
How do I start a QRSPIV work item?
Run /Qrspiv:question with your task description; each subsequent command tells you the next step in the chain.
What makes research objective?
The research phase hides the feature ticket so the agent records codebase facts without forming implementation opinions.
Where are artifacts stored?
Each work item produces a folder under thoughts/ containing task, questions, research, design, outline, plan, and validation files.