mwarger

Bootstrap Forge in the current project. Detects project type, configures validation commands, installs pre-commit hook, and vendors ralph-loop. Use this when setting up a new project for Forge spec runs and bead execution.

Create a subject-named specification from any evidence source using a reducer-based Forge workflow. Use this when the user wants a planning-ready spec, a clean-room reverse spec, or an evidence-first feature spec with sub-agent fanout, provenance tracking, adaptive clarification, speculative variants, and a canonical readiness contract.

Stamp a self-replicating four-bead autoresearch loop (doer/judge/arbiter/strategist) for autonomous iterative improvement of any artifact. Use after interactive intake when you have a program and want to run an autonomous improvement loop with blind scoring. Triggers on: autoresearch, research loop, autonomous loop, overnight loop, iterative improvement.

Decompose an implementation plan into br beads with dependency wiring, epic grouping, and provenance labels. Use this after spec-plan-handoff when the user accepts the beads generation prompt.

Stress-test beads for coverage, granularity, dependency correctness, and actionability using adversarial agent teams. Use this after spec-beads-generate when the beads workspace is populated.

Score a subject spec against the ontology and canonical readiness contract. Use this when you need claim-level coverage scoring, corroboration checks, critical-decision coverage, risk-weighted assumptions, contradiction penalties, and blocker-aware 80/80 gates.

Normalize all starting evidence into a subject spec run. Use this when beginning a Forge spec from code, docs, transcripts, screenshots, URLs, or a sparse user request. Creates the subject slug, frontmatter, evidence ledgers, request archetype, evidence-density classification, and canonical readiness skeleton.

Run the evidence-first Forge loop for a subject spec. Use this when you need to process evidence one unit at a time, produce unit summaries, rewrite the rolling summary, branch out to sub-agents for bounded exploration, choose adaptive clarification profiles, and emit speculative variants when blockers remain.

Stress-test a subject spec for ambiguity, gaps, contradictions, and untestable claims using dynamic agent teams. Use this when the spec has passed completeness and synthesis-review gates and needs adversarial validation before readiness promotion.

Stamp a self-replicating four-bead autoresearch loop (doer/judge/arbiter/strategist) for autonomous iterative improvement of any artifact. Use after interactive intake when you have a program and want to run an autonomous improvement loop with blind scoring. Triggers on: autoresearch, research loop, autonomous loop, overnight loop, iterative improvement.

Decompose an implementation plan into br beads with dependency wiring, epic grouping, and provenance labels. Use this after forge-plan-handoff when the user accepts the beads generation prompt.

Stress-test beads for coverage, granularity, dependency correctness, and actionability using adversarial agent teams. Use this after forge-beads-generate when the beads workspace is populated.

Score a subject spec against the ontology and canonical readiness contract. Use this when you need claim-level coverage scoring, corroboration checks, critical-decision coverage, risk-weighted assumptions, contradiction penalties, and blocker-aware 80/80 gates.

Normalize all starting evidence into a subject spec run. Use this when beginning a Forge spec from code, docs, transcripts, screenshots, URLs, or a sparse user request. Creates the subject slug, frontmatter, evidence ledgers, request archetype, evidence-density classification, and canonical readiness skeleton.

Run the evidence-first Forge loop for a subject spec. Use this when you need to process evidence one unit at a time, produce unit summaries, rewrite the rolling summary, branch out to sub-agents for bounded exploration, choose adaptive clarification profiles, and emit speculative variants when blockers remain.

Create a subject-named specification from any evidence source using a reducer-based Forge workflow. Use this when the user wants a planning-ready spec, a clean-room reverse spec, or an evidence-first feature spec with sub-agent fanout, provenance tracking, adaptive clarification, speculative variants, and a canonical readiness contract.

Stamp reverse process beads with bug investigation question bank for root-cause analysis and fix planning

Stamp decompose process beads — spec → phased work beads with review passes, structural quality gates, and clean-room carry-through

Stamp reverse process beads with feature-specific question bank for deeper business and technical interrogation

Stamp reverse process beads with fast-track hotfix question bank for urgent production fixes

Stamp reverse process beads with refactor question bank for architecture migration and behavioral preservation

Stamp reverse process beads — any input → clean-room spec via bead graph with deep study, draft, fresh-eyes reviews, and consolidation

Ralph Crispies: deep interview for the QRDS-PI cycle. Understands the goal, explores the codebase tactically, then grills the design in small dependency-aware batches with recommended answers. Optimized for voice input. Triggers on: rc-questions, interview, start cycle, new epic, rc questions.

Ralph Crispies: bootstrap QRDS-PI workflow in any project. Sets up beads workspace, copies scripts, installs formula, and installs AGENTS.md workflow instructions. Triggers on: rc-init, rc init, setup ralph, bootstrap.

Ralph Crispies: daily driver for the QRDS-PI cycle. Reads the bead graph, reports state, presents structure for review, handles iteration (send feedback through another pass). Triggers on: rc-next, rc next, what's next, continue, pick up, resume.