---
description: "Quick surgical fix — 1-2 files, no plan. For typo, rename, single-function tweak. Auto-verifies, auto-logs failures to journal, refuses on scope creep."
---

Dispatch the `quick-fix` agent. Pass the user's task description (everything after `/man-quick`) as input.

When the agent returns:

1. Print the receipt verbatim.
2. If verify **FAILED**:
   - Do NOT commit.
   - Dispatch `journal-writer` with: task description, what was attempted, why verify failed, current state (still open).
   - Tell the user: "Verify failed. Logged to journal. Fix the failure or escalate to `/man-fix`."
3. If verify **PASSED**: ask the user "Commit?" — wait for confirmation before staging/committing.
4. If verify **N/A**: tell the user "No verify command available. Review the diff manually before committing."

   **Extended verify (FE files):** If the file changed has extension `.tsx/.jsx/.vue/.svelte`, load skill `browser-testing-with-devtools`. Start dev server, use Chrome DevTools MCP to check DOM/console/network. Report runtime evidence.

   If browser MCP unavailable → skip with note "browser MCP unavailable, manual verify needed".

5. If the agent **refused** (scope too large or vague):
   - Print refusal verbatim.
   - Dispatch `journal-writer` with: original task, refusal reason, suggested tier — so future-you sees pattern of misclassified tasks.
   - Suggest the correct tier (`/man-fix` for debug, `/man-plan` for multi-file).

Never expand scope. Never call `/man-plan` automatically. If the user pushes back on a refusal, restate the cap — escalation is the user's choice.