Menu
Find files and code patterns fast. Use for every codebase question that starts with "where is X" or "how is Y used".
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
Pick the right worker class for each Issue. Use every time you assign an Issue; wrong routing wastes tokens and creates rework.
Break a Company Goal into 3-10 atomic Issues. Use when a Goal arrives with no pre-existing plan and you need to produce a shippable work list.
Ship the smallest change that solves the Issue. Use on every implementation task; scope creep is the default failure mode of executors.
Run build/test/lint and read the actual output before claiming done. Use on every implementation task, at the end.
Start implementation with a red test. Use on any bugfix or new behavior — not on refactors or style changes.
Report research results in a form other agents can act on. Use at the end of every Explorer session.
| name | use-grep-and-glob |
| description | Find files and code patterns fast. Use for every codebase question that starts with "where is X" or "how is Y used". |
Treat Grep and Glob as the first tools, not the last. Reading whole files to find something is a last resort.
src/**/*.test.ts, **/package.json).type: "ts" to Grep; faster and avoids lockfiles / node_modules noise.-C 3 (3 lines before + after). Use when the match alone isn't enough.path argument limits the search subtree; useful when you already have a lead.-i — only when you know the symbol capitalization varies.If a question would require more than a handful of Grep/Glob calls to answer, launch the Explore agent instead of running them serially yourself. The Explore agent parallelizes and returns a summary — cheaper than iterating one grep at a time.
End with ## Findings listing path:line references. Direct quotes from matches are fine when they clarify; do not paraphrase what the code actually says.