using-qrspi

Orchestrate QRSPI pipelines that gate sequential development artifacts.

36|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dfrysinger/qrspi-plus --skill using-qrspi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-qrspi
Source: https://github.com/dfrysinger/qrspi-plus/tree/main/skills/using-qrspi
Command: npx skills add https://github.com/dfrysinger/qrspi-plus --skill using-qrspi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QRSPI enforces a disciplined, review-gated pipeline for agentic software development so projects progress through Goals, Questions, Research, Design, Structure, Plan, Worktree, Implement, Integrate, Test, and Replan with clear artifacts and human approval points, preventing drift and ad-hoc coding.

Core Features & Use Cases

  • Sequential artifact gating: Ensures each step produces reviewable artifacts with status: approved before downstream steps run.
  • Route flexibility and mid-pipeline entry: Supports full and quick-fix routes, route changes before Plan, and resuming runs from approved artifacts.
  • Automated review rounds and backward loops: Runs Claude/Codex reviewers, applies fixes, supports autonomous review loops, and enforces backward loops when new learnings require upstream updates.
  • Use case: Start a new feature or bugfix with explicit acceptance criteria, automated review rounds, and commit checkpoints for each approved artifact.

Quick Start

Begin by invoking the Goals step with the command: start the QRSPI pipeline and create goals.md describing the feature, constraints, and acceptance criteria.

Frequently Asked Questions about using-qrspi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a review-gated agentic development pipeline?

Sequential artifact gating ensures each pipeline step produces reviewable artifacts marked as approved before downstream steps execute. This mechanism prevents unreviewed code changes from advancing through the development workflow.

How do I start a structured pipeline for agentic software development?

To start a structured pipeline, invoke the Goals step to create a goals.md file describing your feature, constraints, and acceptance criteria. This initiates the sequential workflow and generates the first required artifact for review and approval.

Can I resume an agentic development workflow from a mid-pipeline step?

Yes, you can enter mid-pipeline and resume runs from previously approved artifacts. The workflow supports full and quick-fix routes, allowing route changes before the Plan step and enabling flexible iteration on existing software projects.

How do automated review loops work in an agentic coding workflow?

Automated review loops run reviewers to check artifacts, apply fixes, and enforce backward loops when new learnings require upstream updates. This ensures robust iteration by validating artifact presence and approval markers throughout the development cycle.

What are the limitations of enforcing sequential development artifacts?

Enforcing sequential development artifacts requires strict gating rules, meaning steps cannot proceed without explicit approval markers. This disciplined approach may slow down rapid prototyping but ensures robust iteration and prevents drift in agentic software projects.