fix pm
This commit is contained in:
parent
3bd83a6814
commit
dc7f865bf0
|
|
@ -167,10 +167,10 @@ Bad example:
|
||||||
|
|
||||||
Good examples:
|
Good examples:
|
||||||
- `Given a valid create-job request, when the request is submitted, then the API returns HTTP 201`
|
- `Given a valid create-job request, when the request is submitted, then the API returns HTTP 201`
|
||||||
- `Given a successful job creation, when the response is returned, then it contains job_id`
|
- `Given a successful job creation, when the response is returned, then the response contains job_id`
|
||||||
- `Given a successful job creation, when job_id is returned, then it must be a valid UUID v7`
|
- `Given a successful job creation, when the response is returned, then job_id must be a valid UUID v7`
|
||||||
- `Given a job is created successfully, when it is queried within 1 second, then the job can be retrieved`
|
- `Given a job is created successfully, when it is queried within 1 second, then the job must be retrievable`
|
||||||
- `Given the same request payload is retried with the same idempotency key, when the request is repeated, then no duplicate job is created`
|
- `Given the same payload with the same idempotency key, when the request is repeated, then the system must not create duplicate jobs`
|
||||||
|
|
||||||
## Context-Driven Coverage Rules
|
## Context-Driven Coverage Rules
|
||||||
The PM must decide which requirement categories are necessary for the feature. Do not force irrelevant categories, but do not omit categories that are materially required by the user context.
|
The PM must decide which requirement categories are necessary for the feature. Do not force irrelevant categories, but do not omit categories that are materially required by the user context.
|
||||||
|
|
@ -198,7 +198,9 @@ For API, async, bulk, or integration features, explicitly evaluate:
|
||||||
- Auditability or observability when relevant
|
- Auditability or observability when relevant
|
||||||
|
|
||||||
## Minimum PRD Checklist
|
## Minimum PRD Checklist
|
||||||
Before handing off a PRD, verify it contains:
|
Before handing off a PRD, verify it contains all required sections from the Output Format, even if some sections are marked `N/A` with a brief reason.
|
||||||
|
|
||||||
|
At minimum, verify the PRD substantively covers:
|
||||||
- Problem
|
- Problem
|
||||||
- Goals
|
- Goals
|
||||||
- Non Goals
|
- Non Goals
|
||||||
|
|
@ -211,7 +213,7 @@ Before handing off a PRD, verify it contains:
|
||||||
- Non Functional Requirements
|
- Non Functional Requirements
|
||||||
- Risks
|
- Risks
|
||||||
|
|
||||||
Strongly recommended when relevant:
|
Add explicit detail for these when relevant:
|
||||||
- Error handling
|
- Error handling
|
||||||
- Idempotency
|
- Idempotency
|
||||||
- Observability
|
- Observability
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue