mvds-case-study-iteration

IN BUILD

"Lets experiment with writing a combined case study for MVDS. get reviews from all my Voices - strategist, prd writer, designer, etc. … Attempt to generate imagery where possible, or put placeholders with a brief to me to go and produce it. … I want it to populate the draft case study page for MVDS with our progress. … I also want an outcome to be a new case study writing skill (or an updated existing one) that works through the process we do here." — Katy, 2026-09-04

STAGES

  1. proposal09-17
  2. requirements09-17
  3. design09-17
  4. tasks09-17
  5. build—
  6. archived—

CAPABILITIES — 2 IN ONE CHANGE

  • case-study-imagery2 requirements
  • case-study-method3 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1Captured image carries provenance — all six captures carrynot stated
  • ✓1.2Failed capture becomes a brief — slot 2 (three-copies diagram)not stated
  • ✓1.3Figma review precedes Notion embed — Katy approved 02.4 withnot stated
  • ✓1.4Review pages are findable by name — pages 01/02/02.1–02.4 allnot stated
  • ✓1.5A future case study runs from the skill alone — skill rewrittennot stated
  • ✓1.6Panel re-review gates completion — five APPROVEs (below)not stated
  • ✓1.7Tone pass — adjective scan clean; body ≈ 450 words vs thenot stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-09-17 · 1 pull request
    • #456feat(skills): case-study writing guidelines + mvds portfolio draft

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder