| name | product-prd |
| description | Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing. |
Product PRD
Turn an approved problem into testable requirements in the sidecar PRD.md.
- Read sidecar
PROJECT.md, product context, existing PRD, and
references/prd-quality.md.
- Identify users, jobs, pain, outcomes, constraints, dependencies, and
exclusions. Resolve product-changing ambiguity with the user and label
reversible assumptions.
- Give every requirement a stable ID, priority, and observable acceptance
evidence. Cover applicable security, privacy, accessibility, reliability,
performance, data, installation, update, support, and platform needs.
- Separate acceptance by frontend, backend, and integration so an approved
architecture can form a contract and later split disjoint workstreams.
- Keep solution choices out unless they are real constraints. Record user
approval in the sidecar PRD before routing to
solution-architecture.
Do not invent approval, metrics, research, legal requirements, or platform
verification. Do not write project workflow records in the code repository.
