Menu
Quick research — get a sourced answer in under a minute. Use instead of /research when you need a fast answer, not a deep dive.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Capture what was done in the current conversation as a repeatable, well-structured skill (SKILL.md). Interviews the user to clarify intent, scope, and edge cases before writing.
Generate a high-level architecture design document from a requirements document. Covers technology choices, compute platforms, databases, data models, data flows, and security posture — no code snippets or code structure.
Generate a low-level design specification from requirements and high-level design documents. Covers class diagrams, package structure, class interactions, and testing strategy — the bridge between architecture and implementation.
Implement a specific task from the implementation plan using strict TDD. Writes failing tests first, then minimal code to pass, with human approval before committing. Tracks status in plan/{prefix}-plan.md.
Generate an implementation task plan from design documents. Breaks a low-level design into ordered, dependency-aware tasks with explicit parallelization analysis. Use when you have a completed low-level design and need to plan the implementation work.
Diagnose and fix test coverage gaps. Identifies uncovered code paths, adds targeted tests, refactors untestable code, and introduces mocking where needed. Never lowers thresholds.
| name | quick-research |
| description | Quick research — get a sourced answer in under a minute. Use instead of /research when you need a fast answer, not a deep dive. |
| argument-hint | <question or topic> |
| context | fork |
| agent | quick-researcher |
| allowed-tools | Read, Glob, Grep, Bash, WebSearch, WebFetch, Write |
Answer the following question quickly and with sources.
Question: $ARGUMENTS
Be fast and direct. Lead with the answer, cite your sources, and stop. If this question clearly needs deeper investigation, say so and suggest the user run /research instead.
