To plan

Write plans as executable understanding, not executable code. A good plan shows flows, boundaries, composition, and call trees so the executor extends the existing system instead of copying new code into it.

Where this fits

This plan is the last step before code. The artifacts before it have their own owners and formats, which this skill does not impose on: a requirements spec is /to-spec, build tickets are /to-tickets, and open decisions are a /wayfinder map. Those deliberately leave out file paths; this plan adds them. When the requirements or the split into tickets are not settled yet, tell the user to settle them with those commands first, then plan the work of one spec or one ticket here.

Display belongs to show-me

Call the Skill tool with "show-me" before drawing anything. It owns every visual decision: picking the smallest view, call trees, component trees, file trees, pseudocode, Mermaid, and diffs for changes. Use its forms freely. This skill adds no labels, sigils, or drawing conventions of its own.

Plan skeleton

Every plan carries, in order: