Product · AI champion · PM as a builder

The prototype is the spec.

A one-page brief, a skill that turns it into a working prototype, and one PRD from SharePoint rendered as the proof.

0 pagebrief replaces the written spec
0 skillbrief or PRD to working prototype
0 pagesSkills Editor PRD, one working screen
0 checksacceptance criteria the prototype tests on itself
ForProduct managers
StatusKit built. No cohort yet.
ByDallas Andrews, AI champion, Product
Worked exampleSkills Editor PRD v2.0, May 2026
In one screen
  • What changes. A review decides on something people click, not something they read. The brief records the decision; the prototype is the argument.
  • What exists today. The brief template, the pm-prototype skill, and the Harmoniq Skills Editor PRD rebuilt as a working three-panel editor with its eight acceptance criteria tested inside the file.
  • What it needs from Product. The first PM and the first live feature, Claude access for that PM, and a home for prototypes.
What changes

Six pages to read, or one screen to click.

Written spec as the decision artifact
  • Read by each reviewer separately, interpreted differently
  • Layout questions argued in words ("three panels at 1280px?")
  • Acceptance criteria checked after engineering builds
  • The decision lives in meeting notes
Prototype plus one-page brief
  • Clicked by everyone in the same review
  • Layout questions answered by resizing the window
  • Acceptance criteria run by the prototype on itself before the review
  • The decision is written into the brief, section 8
How a PM ships one

Five steps, one owner each.

  • 1Write the briefPMOne page: the decision the prototype settles, who uses it, what it does, five to eight acceptance checks.
  • 2Run pm-prototypePM, in ClaudeThe skill takes the brief (or an existing PRD) and returns a single working HTML file on the Intradiem design system.
  • 3Self-checkPMPress ? in the prototype. Computable checks show pass or fail; the rest are marked manual.
  • 4Review on the prototypePM, design, engineeringThe room clicks through. Answers to the brief's open questions go into the decision record.
  • 5Hand offPM to engineeringPrototype plus brief. A PRD is written afterwards only where a compliance or contract record requires one.
The kit

Three pieces, all in the repo.

Template

Prototype brief

Nine sections on one page. Section 1 is the decision the prototype settles; section 6 the checks; section 8 the decision record.

motions/ai_champion_product/Prototype_Brief_Template.md

Skill

pm-prototype

Brief or PRD in, working single-file prototype out, with the self-check panel and the source saved beside it. Uses the DS v1 tokens from the Skills Editor PRD unless a PM points at another reference.

~/.claude/skills/pm-prototype/SKILL.md

Worked example

Skills Editor

PRD-ICC-S2-001 v2.0 (SharePoint, engineering Aldus documents, May 2026) rendered as the three-panel editor it describes.

motions/ai_champion_product/prototypes/skills_editor/

Worked example

One PRD, rendered as it reads.

The Skills Editor PRD specifies a 256px sidebar, a three-panel editor (roster, dimension tabs, Compare to Template), a save-confirm workflow, and eight acceptance criteria. The prototype implements all of it in one file with no external requests, and tests the criteria on itself.

  • AC-01DS colours: sidebar #F8F8F8, primary buttons #5AB274, active tab underline, no #014637 or #2DB56E in chromecomputed
  • AC-02No emoji in chrome; nav icons are inline SVGcomputed
  • AC-03Business Object tab renders System Objects and insurance classes with counts above zerocomputed
  • AC-04Compare to Template shows all four categories for Sarah Chen; Missing includes Part-D and Medicaidcomputed
  • AC-05Process activity column never shows "undefined"computed
  • AC-06Save persists: reselecting the agent shows the updated levelscomputed
  • AC-07Three panels reflow at 1280px; no horizontal overflow at 1080px and abovecomputed
  • AC-08Primary buttons 36px, 4px radius, 700 14px, letter-spacing .03emcomputed

Result on Aug 31 2026: one file of 78 KB, no external requests, all eight checks computed by the prototype and passing at 1440px and 1080px. Sarah Chen's Compare to Template shows 20 met, 4 below, 2 missing (Medicaid, Part-D), 4 extra. Build time from PRD to passing checks: about seven minutes of agent run, plus the brief. Open Sans and Roboto are declared but not embedded, so a machine without them shows the system font.

What a review on this prototype would settle

The PRD leaves three questions open, and they are the ones a room answers by clicking: whether Compare to Template belongs beside the editor or as a step before Save; whether the right panel dropping under the centre at 1280px is acceptable on laptops; whether Quick Add inserts at level 1 or asks for a level. No review has been held; the example brief records them as open.

Open with Product
  • First PM, first feature. The kit is proven on an existing PRD. The program starts when one PM runs a live feature through it. Product names the PM and the feature.
  • Claude access. AI champions hold licenses; whether each PM does is Product's call and the intake form's.
  • Where prototypes live. A file works from SharePoint or a noindex Pages link. Product picks one so reviews open the same link.
  • When the PRD still gets written. Only where a compliance or contract record requires it; Product confirms which features those are.
Next: walk the kit with the first PM Product names, and run one live feature through steps 1 to 5.
Product · PM as a builder

The prototype is the spec.

A one-page brief, a skill that turns it into a working prototype, and one PRD rendered as the proof.

What changes

A review decides on something people click, not something they read.

Written specRead separately, interpreted differently. Layout argued in words. Criteria checked after the build. Decision in meeting notes.
Prototype plus briefClicked in the same review. Layout answered by resizing. Criteria run before the review. Decision written into the brief.
How a PM ships one

Five steps, one owner each.

Worked example

Skills Editor PRD, six pages to one screen.

8acceptance criteria in the PRD, tested inside the prototype
3panels: roster, dimension editor, Compare to Template
1file, no external requests, opens from SharePoint or a link

Three questions the PRD leaves open are the ones a room answers by clicking.

Open with Product

It starts with one PM and one live feature.

Intradiem · PM as a builder
1 / 5