qrspi-workflow

Orchestrates an eight-phase software development pipeline with gated transitions.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill qrspi-workflow-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qrspi-workflow
Source: https://github.com/bostonaholic/team/tree/main/skills/qrspi-workflow
Command: npx skills add https://github.com/bostonaholic/team --skill qrspi-workflow-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, unverified, and poorly scoped feature development by enforcing a strict, multi-phase workflow that prevents skipping critical steps like research, design review, and verification.

Core Features & Use Cases

  • Phase Discipline: Orchestrates development through eight sequential phases: Worktree, Question, Research, Design, Structure, Plan, Implement, and PR.
  • Gate Enforcement: Implements hard, soft, and advisory gates to ensure quality, security, and design integrity before moving to the next phase.
  • Use Case: Use this to manage complex feature requests where you need to ensure that research is isolated from the final goal, designs are reviewed by peers, and implementation is verified through automated testing and code review.

Quick Start

Invoke the qrspi-workflow skill by initiating a team command to begin the pipeline for your new feature request.

Frequently Asked Questions about qrspi-workflow

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

FAQPage Schema
How do I enforce a strict phase-based workflow for feature development?

Phase-based feature development is enforced by orchestrating an end-to-end pipeline through eight sequential, gated phases to ensure consistency and quality. This prevents skipping critical steps like research, design review, and verification.

What is the best way to prevent scope creep during complex software implementation?

Preventing scope creep during software implementation is achieved by enforcing structural and procedural invariants within a multi-phase development pipeline. This ensures adversarial verification of designs and code before state transitions occur.

How do development pipelines manage artifact generation and state transitions?

Development pipelines manage artifact generation and state transitions by orchestrating complex technical tasks through distinct gated phases. Hard, soft, and advisory gates ensure quality and security before advancing to the next phase.

Can I use gated workflows for isolated research and peer design reviews?

Gated workflows support isolated research and peer design reviews by separating the research phase from the final goal and requiring design reviews before implementation. This ensures feature consistency and quality for complex requests.

When do I need an orchestration pipeline with hard and soft gates?

An orchestration pipeline with hard and soft gates is needed when managing complex feature requests that require strict quality, security, and design integrity checks. It ensures automated testing and code review occur before pull request generation.