Skills › Visual Explainer › visual-explainer › generate-visual-plan.md
generate-visual-plan.md
15 lines · plugins/visual-explainer/commands/generate-visual-plan.md at 9d5f880
Most marks come from matching words in the file, so treat them as pointers.
1---
2name: generate-visual-plan
3description: Generate an interactive visual implementation plan the reader can answer in place
4---
6Load the visual-explainer skill and make a visual implementation plan for: $@
8Follow `references/plans.md`.
101. **Research first:** entry points, affected modules, public APIs, data model and config, tests, similar features, and README/CHANGELOG constraints. Note exact `file:line` and the user's own words.
112. **Write the level-1 claims** and fix them before anything else.
123. **Draw the hero** with `<ve-flow>`: new and removed parts marked, each linked to its claim.
134. **Add how and where claims, then the decisions.** Mark claims you could not confirm `evidence="guess"`; give each level-1 claim a `check`.
145. **Render** (in Pi, `viewer: "glimpse"` sends the response straight back), hand over in one line, and wait. Do not build before the response arrives.
156. **After you build**, set each claim's `status` and render again.
Load the visual-explainer skill and make a visual implementation plan for: $@
Follow references/plans.md.
- Research first: entry points, affected modules, public APIs, data model and config, tests, similar features, and README/CHANGELOG constraints. Note exact
file:lineand the user's own words. - Write the level-1 claims and fix them before anything else.
- Draw the hero with
<ve-flow>: new and removed parts marked, each linked to its claim. - Add how and where claims, then the decisions. Mark claims you could not confirm
evidence="guess"; give each level-1 claim acheck. - Render (in Pi,
viewer: "glimpse"sends the response straight back), hand over in one line, and wait. Do not build before the response arrives. - After you build, set each claim's
statusand render again.
Involves a person and wait :14