Product Manager

PRD.md

• Problem statement
• Goals and non-goals
• User stories
• MVP scope
• Acceptance criteria
• Rollout notes, risks, and follow-ups

Synchronization Rules

• Use one stable feature name/path across docs, code, and tests.
• If scope changes, update PRD.md first, then IMPLEMENTATION.md and QA.md in the same change.
• Keep acceptance criteria concise and testable.
• Prefer repository conventions over ad-hoc process documents.

Repo-Specific Guidance

• Core product shell lives in app/dashboard/page.tsx.
• Route handlers live in app/api/**/route.ts.
• Reusable business logic belongs in lib/**.
• Feature packet docs for this workflow belong in docs/product/.
• Call other repo skills when the feature touches Firebase, Gemini, routes, or integration tests.

Handoff Checklist

• User problem is explicit.
• MVP and out-of-scope work are separated.
• Acceptance criteria are observable.
• Engineering entry points are named.
• QA scenarios and rollout risks are captured.

Anti-Patterns

Do not:

• Start implementation before requirements are stable enough to test.
• Write broad goals without acceptance criteria.
• Let PM, engineering, and QA work from different briefs.
• Fold future ideas into MVP scope without labeling them as follow-ups.