Menu
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.
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.
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.
Find files and code patterns fast. Use for every codebase question that starts with "where is X" or "how is Y used".
| name | issue-decomposition |
| description | 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. |
A good Issue is one worker can own end-to-end in one sitting without blocking on side decisions.
When any of these trip, split it.
Finish with ## Dispatch Summary listing each Issue's id, assigned worker, and its declared dependencies. The user should be able to read it and agree the breakdown is complete — no output that maps to the Goal is missing, no Issue has unclear scope.
