qralph

Orchestrates a deterministic multi-agent pipeline from ideation through deployment and smoke testing.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill qralph-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qralph
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/qralph/skills/qralph
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill qralph-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding assistants often skip tests, rubber-stamp their own verification, and lose track of requirements on long runs. QRALPH wraps Claude Code in a deterministic 14-phase state machine that enforces every step of software delivery — requirements decomposition, TDD, quality gates, fresh-context verification, and post-deploy smoke tests — so nothing gets silently dropped or bulk-approved. ## Core Features & Use Cases - Deterministic 14-Phase Pipeline: IDEATE through COMPLETE, with the Python pipeline script deciding agent selection, model assignment, parallel execution groups, and gate enforcement while Claude does the creative work. - Evidence-Based Verification: A fresh-context verifier checks every acceptance criterion against actual source files with file:line quoted evidence, and quality gates (lint, typecheck, tests) hard-block progression on failure. - Full Lifecycle Automation: Persona generation, concept review, parallel execution with early-start optimization, quality loops with backtracking, demo gates, git branch/PR automation, deployment, smoke tests against the live URL, and cross-project learning capture. - Use Case: Run QRALPH "Add user profile page with avatar upload and privacy settings" and the pipeline decomposes requirements into tracked fragments, spawns parallel implementation agents, runs quality loops until convergence, verifies every criterion independently, and optionally deploys with smoke tests. ## Quick Start Ask the AI to run QRALPH with your project request, for example: run the qralph pipeline to build a landing page with a contact form and deploy it to Cloudflare Workers.

Frequently Asked Questions about qralph

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

FAQPage Schema
How do I run a multi-agent pipeline in Claude Code?▼

Invoke QRALPH with a request string, such as QRALPH "build a landing page". The pipeline script returns one action at a time via the next command, and the executor spawns agents, writes outputs, and confirms gates exactly as instructed until completion.

What is the difference between QRALPH thorough and quick modes?▼

Thorough mode runs all phases including IDEATE, PERSONA, CONCEPT_REVIEW, SIMPLIFY, and LEARN, aimed at non-technical users. Quick mode skips those phases and goes straight from PLAN through execution, verification, demo, deploy, and smoke testing for developers.

Does QRALPH deploy automatically to production?▼

Only with explicit intent. If the request says "deploy to Cloudflare Workers", the pipeline auto-deploys and runs smoke tests. Implicit intent shows a confirmation gate, and requests with no deploy language skip DEPLOY and SMOKE entirely.

How does QRALPH verify that acceptance criteria are met?▼

A fresh-context verifier agent with no knowledge of the implementation checks every acceptance criterion against actual source files. Each criterion requires file:line evidence with quoted code, and a FAIL or ambiguous verdict blocks finalization.

Can QRALPH resume after a session crash or interruption?▼

Yes. State is checkpointed at every phase transition in .qralph/projects/<id>/state.json. Running the pipeline's next command with the project ID resumes exactly where it left off, and multiple projects can run concurrently with isolated state.

What happens when the QRALPH quality loop finds problems?▼

The quality loop separates discovery from fixing, tracks P0/P1/P2 findings per round, and detects stagnation or regressions. If architectural issues surface, the pipeline backtracks to PLAN (up to twice) rather than forcing fixes onto a broken design.