Part A works, and some part of your brain still wants to see the board. So we build one, and we're clear about what we're not doing: we're not building an app. One prompt produces a single HTML page in the repo, one column per stage folder, a card per prospect with value, next action, and days in stage, with stale deals highlighted. Double-click it and it opens. Then bm-skill-builder adds an update-dashboard skill that process-inbound calls as its last step, so the board is never stale. We talk about how a page with no server reads files, why the files stay the truth, and where the real-app upgrade path leads.
What's covered:
- Asking for the outcome, not the mechanism: a board that opens on double-click
- Columns as stage folders, cards as activity files
- Highlighting stale deals so you can see them from across the room
- The update-dashboard skill, added as the last step of intake
- Skills invoking skills, named as a pattern
- Why the files stay the truth and the page is just a picture
- The upgrade path to a real hosted app