feat: add PRD template for scoping larger features

.github/ISSUE_TEMPLATE/prd.md

@@ -0,0 +1,41 @@
+---
+name: New PRD
+about: Propose and scope a feature or change that touches multiple subsystems, the data model, or public API/behavior
+title: 'PRD: '
+labels: ''
+assignees: ''
+---
+
+<!-- Keep it short — 1-2 pages, not a process. For small, well-understood
+     fixes, just open a plain issue instead. See docs/templates/PRD.md. -->
+
+## Problem
+
+<!-- What's broken or missing, and for whom? If this section doesn't answer
+     "why are we building this," the rest doesn't matter. -->
+
+## Non-goals / out of scope
+
+<!-- Explicit. Prevents scope creep and sets reviewer expectations. -->
+
+## Proposed solution
+
+<!-- The approach, in enough detail for a contributor to start implementation
+     without re-deriving the design. -->
+
+## Alternatives considered
+
+<!-- Briefly, with why they were rejected. -->
+
+## Technical approach / affected areas
+
+<!-- Which parts of backend/, frontend/, or schema.sql this touches. -->
+
+## Success metrics
+
+<!-- How we'll know it worked, even informally (e.g. "eliminates issue
+     class X", "no perf regression on Y"). -->
+
+## Open questions
+
+<!-- Things the author knows they don't know yet. -->

.gitignore

@@ -27,3 +27,8 @@ e2e/.auth/
 # harness only; CI scaffolds its own fresh copy on every run
 /supabase/
 backend/supabase/
+
+# dev-cycle scratch files
+.current-issue.md
+.implementation-plan.md
+.implement-config

CONTRIBUTING.md

@@ -4,6 +4,7 @@ Thanks for helping improve Mike. Please keep contributions small, focused, and e
 
 ## Guidelines
 
+- For changes that touch multiple subsystems, the data model, or public API/behavior, open a PRD issue first using the "New PRD" template (`docs/templates/PRD.md`); for small, well-understood fixes, a plain issue is fine.
 - Prefer targeted edits over broad refactors.
 - Keep each PR focused on one bug, feature, or cleanup.
 - Update docs or env examples when changing setup, config, or user-facing behavior.

docs/templates/PRD.md

@@ -0,0 +1,37 @@
+# PRD: <title>
+
+<!-- Copy this template into a new GitHub issue (or use the "New PRD" issue
+     form) when scoping a feature or change that touches multiple subsystems,
+     the data model, or public API/behavior. Keep it short — 1-2 pages, not a
+     process. For small, well-understood fixes, just open a plain issue. -->
+
+## Problem
+
+<!-- What's broken or missing, and for whom? If this section doesn't answer
+     "why are we building this," the rest doesn't matter. -->
+
+## Non-goals / out of scope
+
+<!-- Explicit. Prevents scope creep and sets reviewer expectations. -->
+
+## Proposed solution
+
+<!-- The approach, in enough detail for a contributor to start implementation
+     without re-deriving the design. -->
+
+## Alternatives considered
+
+<!-- Briefly, with why they were rejected. -->
+
+## Technical approach / affected areas
+
+<!-- Which parts of backend/, frontend/, or schema.sql this touches. -->
+
+## Success metrics
+
+<!-- How we'll know it worked, even informally (e.g. "eliminates issue
+     class X", "no perf regression on Y"). -->
+
+## Open questions
+
+<!-- Things the author knows they don't know yet. -->