Menü
Produce a plan an Executor who has no shared context can follow. Use at the end of every Planner session.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 | write-implementation-plan |
| description | Produce a plan an Executor who has no shared context can follow. Use at the end of every Planner session. |
A plan is not a description of what the code already does — it's a script an Executor can follow. If the Executor has to re-derive your reasoning to implement it, your plan failed.
path:line.End with ### Critical Files for Implementation — 3-5 bullet points with absolute or workspace-relative paths. These are the files the Executor will open first. If fewer than 3 or more than 5 feel right, re-scope the plan.