orc-quick

What problem does it solve? Small coding tasks and quick questions often get over-engineered by heavy multi-phase pipelines, or handled without any record of what was decided and why. This Skill provides a lightweight three-step lane — look, ask once, do — that dispatches a user-chosen agent for each task and saves every request as a numbered entry in a persistent context document. ## Core Features & Use Cases - Three-step request handling: Each request runs a silent dig to find relevant files, one combined question turn (clarifications plus agent selection), then a dispatch with build/test checks and a written doc entry. - Mandatory dispatch gate: The user picks the executor, recon model, or reviewer before every dispatch; no config key (including opus5_only) can override or pre-answer this choice. - PR comment workflows: Reads pull request review threads via gh, lets the user pick which threads to fix with per-thread agent gates, and never writes replies, approvals, or merges to GitHub. - Persistent context log: Every request — including read-only investigations — is appended as a numbered entry to orc-quick/<slug>/quick-context.md with decisions, dispatches, files changed, and outcomes. - Use Case: Ask it to "fix the review comments on PR 142" — it fetches the threads, asks which to take and which executor to use per thread, applies the fixes, runs build and tests, and records the outcome before offering to commit. ## Quick Start Ask the skill to quickly find and fix why the orders endpoint returns a 500 error, choosing the executor when prompted.