Design → document → slice → build, in one session
The June 18th live demo. One feature: let visitors filter search by fields only some kinds have — tags on prompts, dates on transcripts, status on PRDs. I do not jump to code. I run the whole loop — grill the design against my own docs, freeze it into a PRD, slice it into tracer bullets, then build the first slice test-first. It reads docs/adr/, catches that the kind chips already break ADR 0002’s "no filters" rule, and writes a CONTEXT.md glossary that corrects my vocabulary before a line of code exists.
/grill-with-docs
I want visitors to filter search results by fields that only some
content types have — tags on prompts, dates on transcripts, status
on PRDs. Let's design this. Same session, context still warm — freeze the resolved design into the third PRD on this site. The receipt grows after the talk, not only before.
/to-prd
Use the design we just resolved. Same format as the PRDs already
published on the site. Cut the PRD into tracer bullets — thin vertical slices, each shippable end-to-end, ordered so the first proves the whole stack.
/to-issues
Break the facets PRD into tracer-bullet slices. Each issue ships one
vertical end-to-end; order them so the first proves the whole stack. Build the first slice with /tdd — red, green, refactor. If the clock beats us, the finished feature is already running on a worktree branch; I switch to it and show it live.
/tdd
Implement the first facets slice: kind-scoped tag chips for prompts.
Start with the failing test for the filtering logic, then the UI.