feat: add QRSPI workflow for complex creative challenges#282
Merged
Conversation
…in to schema The state-machine-schema.json was missing three fields widely used by existing workflows: - allowed_file_patterns (state level) - review_perspectives (transition level) - domain (metadata level)
QRSPI (Questions, Research, Design, Structure, Plan, Implement) is a 7-state workflow inspired by the QRSPI methodology. Unlike EPCC (medium-complexity features), QRSPI targets creative, complex challenges requiring deep alignment before execution. Key features: - 4 read-only alignment phases (questions, research, design, structure) - Explicit user-approval gate at design→structure transition - Vertical slice requirement in structure phase - Review perspectives: product owner (design), architect+security (plan), senior dev+performance (implement) - Loop-back transitions from downstream phases to design when approach proves unworkable
…eparation Rewrote all phase instructions from verbose STEP-by-STEP checklists to concise principle statements. Each phase now has a single **Principle** line + goals + explicit 'Do not' constraints. - questions: 'Clarify intent before exploring solutions' — do not research/design/plan/code - research: 'Gather facts before forming opinions' — do not propose solutions/design/code - design: 'Align on WHAT and WHY before detailed HOW' — do not plan implementation/code - structure: 'Decompose into end-to-end testable units' — do not plan tasks/code - plan: 'Define detailed HOW per slice' — do not change design/code - implement: 'Execute plan one slice at a time' — adapt tactics, loop back only if fundamentally flawed - commit: 'Leave codebase cleaner than found' — do not add features File: 373 → 245 lines (-34%). All 7 states, 3 review gates, 19 transitions preserved.
…riven style Commit phase now has Cleanup / Documentation / Validation sections instead of being over-condensed to a single paragraph. Other 6 phases remain concise principle-driven.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces the QRSPI workflow — a 7-state state machine designed for creative, complex challenges requiring deep alignment before execution. It also updates the JSON schema to include three missing fields used by existing workflows.
What's New
QRSPI Workflow (
resources/workflows/qrspi.yaml)QRSPI stands for Questions → Research → Design → Structure → Plan → Implement → Commit
Unlike EPCC (which targets medium-complexity features), QRSPI emphasizes:
design → structure(no auto-transition; requiresproceed_to_phasetool triggerdesign_approved)design → structure: product owner reviewplan → implement: architect + security expert reviewimplement → commit: senior developer + performance engineer reviewstructure,plan, andimplementcan all transition back todesignvianeed_design_changeswhen the high-level approach proves unworkablequestionsSchema Fix (
resources/state-machine-schema.json)Added three fields that were missing from the schema but widely used by existing workflows:
allowed_file_patternsat the state levelreview_perspectivesat the transition leveldomainat the metadata levelTesting
Checklist