Specs & requirements

prd, spec, product requirements, requirements doc, ticket, jira ticket, user story, acceptance criteria, feature spec, scope this, epic, definition of done, backlog item, one-pager, technical spec, rfc

1. +Deliverable + featureProduce a lightweight PRD: problem, goals, user stories, functional requirements, acceptance criteria, non-goals, open questions.
2. +Problem & user / why nowState the assumed user, the problem it solves, and the business reason; flag these as assumptions to confirm.
3. +In-scope vs non-goalsDefine a minimal v1 and an explicit 'Non-goals / later' section for anything adjacent.
4. +Acceptance criteria / definition of doneWrite testable, checkbox / Given-When-Then criteria covering happy path, empty/error states, and edge cases.
5. +Constraints (tech, timeline, compliance)Assume the current stack; note timeline and compliance as open questions; never fabricate SLAs or metrics.
6. +Document shape / sectionsStandard PRD sections with headers, skimmable with a short summary up top; match artifact weight to the ask.
7. +Prioritization / phasingTag each requirement P0/P1/P2 or split into v1 vs later phases.

Left out for this type: role ('expert product manager'); 'professional and engaging' tone; padding v1 with speculative features; inventing SLAs/metrics as fact; marketing/benefit-selling in the spec body; over-formatting a 2-line ticket into a full PRD