菜单
Use when starting any conversation — establishes the QRSPI pipeline for agentic software development, requiring structured progression through Goals, Questions, Research, Design, Phasing, Structure, Plan, Parallelize, Implement, Integrate, Test, with Replan firing between phases
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when questions.md is approved and the QRSPI pipeline needs objective codebase and web research — dispatches parallel specialist subagents per question, collates per-question findings into research/summary.md
Use when starting a new QRSPI pipeline run — captures user intent and constraints through interactive dialogue, then synthesizes a problem-framed goals.md
Per-phase implementation orchestrator. In full pipeline mode, resolves symbolic bases from parallelization.md to concrete commits, creates worktrees and stage commits, runs baseline tests, dispatches implementer + reviewer subagents per task per the wave schedule, runs the fix loop, presents the batch gate, and routes to the next route step (typically Integrate). In quick-fix mode, dispatches the single task (or a fix-task batch from fixes/{type}-round-NN/) through the same per-task implementer + reviewer flow, presents the batch gate (with quick-fix-mode menu), and routes to Test.
Per-phase implementation orchestrator. In full pipeline mode, resolves symbolic bases from parallelization.md to concrete commits, creates worktrees and stage commits, runs baseline tests, dispatches implementer + reviewer subagents per task per the wave schedule, runs the fix loop, presents the batch gate, and routes to the next route step (typically Integrate). In quick-fix mode, dispatches the single task (or a fix-task batch from fixes/{type}-round-NN/) through the same per-task implementer + reviewer flow, presents the batch gate (with quick-fix-mode menu), and routes to Test.
Use when starting any conversation — establishes the QRSPI pipeline for agentic software development, requiring structured progression through Goals, Questions, Research, Design, Phasing, Structure, Plan, Parallelize, Implement, Integrate, Test, with Replan firing between phases
Use when research/summary.md is approved and the QRSPI pipeline needs an architecture — proposes approaches, surfaces key architectural decisions with rationale, and defines per-goal acceptance through interactive design discussion
| name | using-qrspi |
| description | Use when starting any conversation — establishes the QRSPI pipeline for agentic software development, requiring structured progression through Goals, Questions, Research, Design, Phasing, Structure, Plan, Parallelize, Implement, Integrate, Test, with Replan firing between phases |
Read skills/using-qrspi/references/workspace-layout.md when setting up a new run's on-disk layout or auditing an existing one — artifact/code separation (docs/qrspi/{slug}/ vs target repo) and the greenfield bootstrap note.
Read skills/using-qrspi/references/pipeline-overview.md when you need the full pipeline shape — both diagrams (full + quick-fix) and the per-step what/why/artifact table.
Read skills/using-qrspi/references/route-templates.md when Goals is seeding config.md.route at run start, or when the user requests a mid-pipeline route change — quick / full / full-plus-UX templates plus the route-change rules.
Read skills/using-qrspi/references/artifact-directory.md when creating the artifact directory for a new run, or when resolving the slug for an existing run — full per-run on-disk tree (docs/qrspi/YYYY-MM-DD-{slug}/...) and slug-generation rule.
QRSPI dispatch scripts operate under a two-root topology contract: plugin assets and user artifacts live in different trees and must be configurable independently.
PLUGIN_ROOT — immutable plugin assets (skills/, agents/, scripts/, scripts/lib/). Derived from the dispatch wrapper's own location (scripts/..). Override via QRSPI_REPO_ROOT for tests. REPO_ROOT is a back-compat alias.ARTIFACT_ROOT — the user repo where artifacts live and git diff runs. Resolved by precedence (same 4-step ladder on both dispatch-agent.sh and dispatch-companion.sh launch): (1) QRSPI_ARTIFACT_ROOT env var, (2) --artifact-repo-root <path> flag, (3) git rev-parse --show-toplevel discovered from --output-dir (or --round-dir on companion launch), (4) fall back to PLUGIN_ROOT. dispatch-companion.sh await does NOT parse --artifact-repo-root and derives its trust anchor for the round directory from $PWD/.. (the await-round.sh cwd contract) rather than from the job record; $QRSPI_ARTIFACT_ROOT env still applies to ARTIFACT_ROOT resolution in await as in launch.The two roots may coincide (vendored-submodule install, where the artifact directory lives inside the QRSPI repo itself) or diverge (Copilot CLI plugin install, where ~/.copilot/installed-plugins/qrspi-plus/ carries the assets and the user repo carries the artifacts). Skills and scripts MUST NOT assume a single shared root.
Path-guard wiring inside dispatch scripts:
--agent-file, --skill[*], --companion for plugin assets) use assert_path_under_plugin_root (or the legacy assert_path_under_repo_root alias).--artifact, --diff-file, --task-def, --subject-code, --artifact-body, --output-dir, companion-launch --round-dir / --prompt-file) use assert_path_under_artifact_root.Read skills/using-qrspi/references/approval-markers.md when transitioning a step to status: approved (or replan-draft), or before the post-approval git commit — semantics and commit rule.
Pipeline state is derived from artifact frontmatter; the only piece of derived state worth persisting is phase_start_commit (lives in plan.md frontmatter, scoped by Replan and Test).
Read skills/using-qrspi/references/state-and-pipeline-ordering.md before dispatching a downstream step when checking predecessor-approval gating — predecessor rules and the Implement batch trap. Orchestration-boundary enforcement lives in each phase SKILL (implement/, integrate/, test/).
When the user rejects an artifact at a human gate, the current step re-runs with feedback until approved — never skips backward. For subagent-dispatching steps (Plan, Parallelize, Structure), the orchestrator launches a new subagent round with the original inputs plus a feedback file (see Feedback File Format below). For conversational steps (Goals, Design), the rejection iterates in-conversation without writing a feedback file.
Read skills/using-qrspi/references/backward-loops.md when a downstream step surfaces new learnings about an upstream artifact — cascade-forward rule.
Users can enter mid-pipeline when required input artifacts already exist with status: approved; mid-pipeline resume also detects replan-pending.md to resume Replan when set.
Read skills/using-qrspi/references/mid-pipeline-entry.md when resuming a run partway through the pipeline (artifact directory already exists, some steps already approved) — full resume contract and existing-artifacts handshake.
Read skills/using-qrspi/references/pipeline-progress.md when unsure where the run currently sits in the pipeline — diagnostic for resolving ambiguous status.
!cat skills/using-qrspi/references/artifact-gating-check.md
config.md)Read skills/using-qrspi/references/config-runtime-contract.md when validating any config.md field, dispatching an agent, resolving a model_routing: tier, or handling a runtime-backfill write — dispatch routing blocks (providers:, model_routing:, trusted_path:, validators:), Precedence chain, Config Validation Procedure, no-silent-defaults rule, runtime-backfill carve-outs + hard-stop on write-back failure, field-validation-by-skill table. The authoring side (format, field definitions, writing procedure, pipeline: quick semantics) lives at skills/goals/references/config-md-authoring.md and is !cat-included into Goals — read it directly only when auditing Goals' config-writing behavior.
Every artifact-producing step runs the Standard Review Loop. Read skills/_shared/review-loop.md when dispatching reviewers, computing kept findings, or deciding fix-loop convergence — canonical SSoT (checklist + reviewer dispatch shape + convergence rule). Sweep-task findings ride the existing Plan re-spec loop (no new gate, no new runner behavior).
After each review round, the orchestrator invokes scripts/review-prep.sh (per-round diff emission with anchor-SHA narrow-ref, atomic temp+rename) then scripts/verifier-fan-in.sh (SSoT for verifier dispatch, change_type-keyed score filters, round-NN-verified.md assembly). Read skills/using-qrspi/references/apply-fix-protocol.md after verifier-fan-in.sh emits round-NN-verified.md, when applying fixes for the round — the full post-fan-in procedure (partition by change_type, scope-tagger dispatch, dispositions.md, per-round commit, convergence rule, backward-loop reset, reviewer-model audit-field, verifier-round failure menu). Read skills/using-qrspi/references/fix-altitude-rule.md when a finding contains the phrase "X is under-specified" — the F-5 altitude rule.
Inside an autonomous review loop (option 2 from the Standard Review Loop), the loop pauses when reviewers surface findings the orchestrating skill cannot safely auto-apply. The 10-round review-loop cap does not decrement on a paused round — paused rounds are user-interactive, not autonomous.
Read skills/using-qrspi/references/review-loop-pause-gate.md when the review loop hits the pause gate (review-round kept-findings non-zero, or a sub-threshold rescue is being surfaced) — full BATCH-WITH-OVERRIDES UI contract, 3-option menu (apply / skip / loop-back to upstream), infinite-pause escape hatch, and pending-findings audit-file shape.
QRSPI skills mark transition points where main-chat context bloat degrades downstream quality. At every checkpoint and at every user-input pause, the orchestrator follows the Iron Rule below — regardless of perceived utilization, regardless of auto-mode.
Iron Rule. Pause and recommend /compact to the user before continuing. The user can decline; do not skip the recommendation.
Read skills/using-qrspi/references/compaction-checkpoints-detail.md when approaching a context-saturation checkpoint and unsure which trigger applies for the current step — full list of checkpoint trigger points per pipeline step.
Read skills/using-qrspi/references/feedback-file-format.md when writing or consuming a feedback file after a rejection round in Plan, Parallelize, or Structure — {artifact-dir}/feedback/{step}-round-{NN}.md YAML+markdown schema. Goals/Design rejection flows interactively and does not produce feedback files.
!cat skills/using-qrspi/references/common-rationalizations.md
!cat skills/using-qrspi/references/iron-laws.md