executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
whiteboard-to-specTurn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and fl…
Independent GitHub snapshot · Automated classification · Original documentation governs
The whiteboard is where teams decide; the photo of it is where decisions go to die. This skill reads the photo like the person who was in the room — arrows, crossings-out, shorthand, spatial grouping — and produces the write-up that should have been made that afternoon.
[illegible — looks like "…"] in the ambiguity ledger. A wrong guess presented confidently poisons the whole spec.What the board says (transcription by region): [region] — [contents, verbatim where legible]
Decisions on the board:
| # | Decision | Evidence on the board | Confidence |
|---|---|---|---|
| [e.g. "circled, arrow from both options"] | high / read-between-lines |
Flows / structures (redrawn):
[the diagram the board was drawing]
Considered and rejected: [crossed-out items, with what replaced them]
Open questions from the board: [every "?", disagreement marker, or dangling arrow]
Ambiguity ledger: [illegible or two-way-readable items — for the room to resolve]
Suggested next step: [the one action the board implies, e.g. "confirm decision #2 with the two owners named"]