Menu
Pick the 3-5 files that an Executor must open first. Use as the last step of writing any implementation plan.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | identify-critical-files |
| description | Pick the 3-5 files that an Executor must open first. Use as the last step of writing any implementation plan. |
The Critical Files list is a scheduling hint for the Executor. Five good files save more time than fifty marginal ones.
A file is "critical" if one of the following is true:
A file is NOT critical just because it is large, "relevant", or "you might want to read it".
foo.ts and foo.test.ts if reading the test adds nothing).List between 3 and 5 files with path-from-workspace-root. No more, no fewer. If you genuinely cannot meet the bound, the plan itself is mis-sized — go back and re-scope.