accelint-qrspi-propose
Use this skill when the user wants to start the formal QRSPI/OpenSpec planning workflow for a ticket, bug, feature request, or proposed product/CLI/app change before implementation. Invoke it when the user wants a spec-driven change package with questions first, factual research, proposal/design artifacts, affected specs, and a vertically sliced task plan, with explicit review/approval stops before any coding begins. This is the right skill when the user wants to plan, scope, or break down the change itself, especially if they ask to use QRSPI, create an OpenSpec change, run a planning workflow, or stop before writing code. Do not use it to implement an existing spec, review or polish artifacts that already exist, generate generic architecture docs, archive completed changes, or support loose brainstorming without a request for formal QRSPI/OpenSpec outputs.
accelint · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add gohypergiant/agent-skills --skill accelint-qrspi-proposeAbout this skill
name: accelint-qrspi-propose description: Use this skill when the user wants to start the formal QRSPI/OpenSpec planning workflow for a ticket, bug, feature request, or proposed product/CLI/app change before implementation. Invoke it when the user wants a spec-driven change package with questions first, factual research, proposal/design artifacts, affected specs, and a vertically sliced task plan, with explicit review/approval stops before any coding begins. This is the right skill when the user wants to plan, scope, or break down the change itself, especially if they ask to use QRSPI, create an OpenSpec change, run a planning workflow, or stop before writing code. Do not use it to implement an existing spec, review or polish artifacts that already exist, generate generic architecture docs, archive completed changes, or support loose brainstorming without a request for formal QRSPI/OpenSpec outputs. license: Apache-2.0 metadata: author: accelint version: "1.9.0"
Accelint QRSPI
Automate the QRSPI + OpenSpec planning workflow. This skill applies the methodology from "We Got RPI Wrong" through OpenSpec's artifact system. It orchestrates the Questions → Research → Design → Structure stages and requires human checkpoints before any code is written.
What This Skill Does
Automates: The planning phase of spec-driven development using QRSPI Scope: Questions → Research → Design → Structure/Plan (stops before implementation) Output: A complete OpenSpec change ready for the accelint-qrspi-apply skill
Does NOT: Implement code, run tests, create PRs, or archive changes
Prerequisites
This skill requires the expanded OpenSpec workflows (explore, new, continue) to access the step-by-step artifact generation.
To verify these workflows are enabled:
openspec config list
Check that the workflows: section includes: explore, new, and continue.
If any are missing, enable the expanded profile:
openspec config profile
# Select "expanded" from the list
openspec update
Workflow Overview
┌─────────────────────────────────────────────────────────────────┐
│ Stage Context Output Checkpoint │
├─────────────────────────────────────────────────────────────────┤
│ Questions Ticket only Questions — │
│ Research Questions only Research doc — │
│ Design Q+R (NO ticket) proposal.md — │
│ design.md — │
│ [STOP HERE] │
│ ⚠️ CHECKPOINT 1: Review design.md - MUST approve to continue │
│ (frontmatter: specs_touched/decisions/created_at -> design.md) │
│ │
│ Specs/Tasks Q+R+design specs/* — │
│ tasks.md — │
│ ⚠️ CHECKPOINT 2: Review tasks.md - MUST approve to continue │
│ │
│ Done — Exit — │
└─────────────────────────────────────────────────────────────────┘
Note: Keep the ticket OUT of context after the Questions stage to prevent completion bleed.
REQUIRED: The Design stage (steps 17-26) generates ONLY `proposal.md` and `design.md`, optionally creates `q-and-a.md` if `--verbose` flag was set, then STOPS for review at step 27. The Specs/Tasks stage (steps 33-43) generates `specs/*` and `tasks.md` separately after design approval.
Capture frontmatter at step 31 after Checkpoint 1 approval, not before. `design.md` reaches its final form for this planning pass only after the user approves it or confirms a manual edit. Earlier capture can write `specs_touched/decisions/created_at` against content the user is about to change. The `created_at` timestamp marks when the user approved the design (the moment the change becomes "real").
⚠️ REQUIRED CHECKPOINTS: The agent MUST pause and wait for explicit user approval at both checkpoints (step 27 and step 44). Proceeding without approval bypasses QRSPI's core value.
Implementation Steps
Execute these steps in order without stopping between them.
-
Validate user input and parse flags: Check if the user provided a ticket, feature request, or idea in their prompt (either as skill arguments or in their message). Also check for the
--verboseflag.Flag parsing:
- Check if the user's input contains
--verbose(with or without other content) - Store the verbose flag state for use in step 25
- Remove
--verbosefrom the input before extracting the ticket description - Store the original input text (after flag removal) for use in step 25 — this will be saved to trace.md if --verbose was set
Validation: If the prompt is empty or contains only the skill invocation with no actual content (after removing flags):
I need a ticket or feature description to plan. Please provide: - A ticket ID and description (e.g., "ATI-123: Add user authentication...") - A feature request ("I want to add dark mode support...") - An idea or problem statement ("Users complain about slow search...") Then I'll use QRSPI to break it down into a structured plan. Optional flags: --verbose Save input, questions, and answers to trace.md for audit trailExit the skill and wait for the user to provide input. Do NOT proceed with internal examples or placeholder content.
- Check if the user's input contains
-
Tell the user: "Checking OpenSpec configuration..."
-
Run
openspec config listand parse the output -
Check if the
workflows:section contains all three required workflows:explore,new, andcontinue -
If any are missing:
This skill requires the expanded OpenSpec workflows (explore, new, continue). Your current workflows: [list what's enabled] Missing: [l