letsmake-product-workflow

Paths: paths.md + .cursor/letsmake.config.json in the consumer workspace; after bootstrap prefer the {docsProductRoot} copies (default docs/product/). Run the install script (install-letsmake.sh / .ps1) if config is missing. Ask via AskQuestion where available, plain chat otherwise.

LetsMake Product Workflow

Orchestrate medium/large product work before engineering owns spec.md. This skill routes; the process itself is stated once in the canonical doc — read the phase you are entering, not the whole thing.

Canonical doc: letsmake-product-workflow.md · Cheat sheet: cheat-sheet.md · Shared rules: letsmake-conventions.md

Artifact map

discovery.md       Living — brief, grill capture, research, design links
gap-analysis.md    Audit — coverage, scope drops, PO decisions log (never inlined in requirements)
requirements.md    SSOT — Consolidated after gap pass (TBC allowed with owners)
decisions.md       PDR log — append-only; supersede, never edit
scenario-matrix.md Pre-handoff edge-case audit
dev-handoff.md     Phase 4 package note
spec.md            Engineering — stub at handoff; eng fills [ENG] sections
design.md          Journeys, screens (may lead or follow discovery)
brief.md           Optional intent summary

Conflict rule: requirements.md (Consolidated) wins over decisions.md > discovery capture, PRDs, chat.

Phases → skills

Phase	Skill / action
0 — Intake	intake-synthesize — destination, track (standard / design-first / spike-only / small change), scaffold
1 — Brief	MoSCoW titles in discovery.md § Brief summary (optional brief.md)
2 — Grill + research	grill-me (captures as it goes) + auto-launched research-spike in parallel; design-first → figma-parity-playbook.md
3 — Gap pass	gap-pass — Phase A questions → PO approval → Consolidated requirements.md; already Consolidated + a wave of updates → increment-requirements
3.5 — Scenario hardening	scenario-hardening — edge-case pass unless small/low-risk and PO accepts N/A
4 — Dev handoff	dev-handoff — Definition of Ready check, handoff note, spec.md stub
5+ — Engineering	Engineering fills spec.md [ENG] sections + implementation plan — not BA-owned

Small changes bypass the full path: small-change-requirements (escalation triggers in small-change-process.md). Unsure → which-skill-next. Doc health → wiki-lint.

Boundaries (enforced across all phases)

• The PO decides product direction; agents propose and capture. Scope drops, requirement content, and TBC resolution go through a question — never a silent merge.
• Only gap-pass and increment-requirements write product content to requirements.md; research never does.
• Research auto-launches on gaps/ideas (parallel default) and produces proposals the PO adopts per item.
• Do not auto-generate requirements.md straight from a brief to bypass gap pass on grill/design-led features.

Full shared rules and anti-patterns: letsmake-conventions.md.