/dr-quick

Overview

/dr-quick is a lightweight fast-lane for tiny, self-contained code fixes or quick information lookups. It deliberately skips the heavy pipeline (PRD, planning, design, QA, compliance) to reduce preparation for a small task.

Usage

/dr-quick "<short task title>"

Note: the title defaults to English unless the operator's content language is set otherwise.

What it does

The request is classified first. A read-only lookup declares its acceptance cases in the conversation, searches read-only, and reports the result as informational / UNCERTIFIED: no task ID, metadata, archive or branch change is created. A mutating fix follows the steps below; it skips the full QA and compliance stages but never the acceptance/evidence floor — falsifiable cases and a preflight receipt before the edit, and a passing check-live-evidence.sh --stage quick before closure.

1. Assigns the next QCK-XXXX task id using the deterministic formula max(claimed across archive ∪ tasks.md ∪ backlog.md) + 1. The ID is not announced until the 3-surface collision probe completes; if the candidate is already claimed (parallel-session race), it auto-bumps to the next free ID. (QCK is a universal area-prefix, archived under quick/.)
2. Appends a thin task line to the active index.
3. Spawns ONE quick context-scan subagent on the runtime's cheapest reasoning tier to locate where the change belongs.
4. Applies the fix or reports the located item.
5. Confirms the delivered commit is reachable from origin/main; failed reachability blocks closure.
6. Writes a short archive entry (what was done + files touched + diff reference) — no reflection, no compliance.

When to use

One-file or few-line fixes, typo/config tweaks, "where is X" lookups.

When NOT to use

Anything needing design, multiple files with shared state, security-sensitive logic, or architecture — use /dr-init for the full pipeline.

Reporting the result

Apply Human Outcome Reporting before a human-facing update or result. Explain the user-visible outcome, the original conditions, checks and evidence, and open limitations. A stage result does not mean the entire task is complete. Keep exact protocols and technical records intact. To explain again without continuing work, use /dr-explain.