Rewrite Prd Section.prompt

---
description: "Rewrite a weak PRD section into compliant FR/NFR/AC requirements using the project requirements writing standards."
name: "Rewrite PRD Section to FR/NFR/AC"
argument-hint: "Paste weak PRD section text and optional context"
agent: "agent"
---

Rewrite the provided PRD section into clear, testable, and consistent requirements.

Use these standards as the source of truth:
- [Requirements Writing Standards](../instructions/requirements-writing.instructions.md)

## Task
Transform weak, vague, or mixed PRD prose into:
- Functional requirements (FR)
- Non-functional requirements (NFR)
- Acceptance criteria (AC)

## Rules
- Keep output product-focused, not implementation-focused.
- Use consistent IDs:
  - FR-1, FR-2, ...
  - NFR-1, NFR-2, ...
  - AC-1, AC-2, ...
- Use normative wording:
  - SHALL for mandatory
  - SHOULD for recommended
  - MAY for optional
- Make each requirement atomic and objectively testable.
- Quantify quality terms where possible (for example: latency, availability, completion rate).
- Ensure each major FR has one or more linked AC items.
- Preserve original intent; do not invent unrelated scope.
- If information is missing, add a TBD note rather than guessing.

## Input Expected
- Weak PRD section text
- Optional context:
  - feature name
  - user type
  - constraints
  - success goals

## Output Format
### Rewritten Requirements
#### Functional Requirements
- FR-1: ...
- FR-2: ...

#### Non-Functional Requirements
- NFR-1: ...
- NFR-2: ...

#### Acceptance Criteria
- AC-1: Given ..., when ..., then ...
- AC-2: Given ..., when ..., then ...

### Traceability
- FR-1 -> AC-1, AC-2
- FR-2 -> AC-3

### Assumptions and TBDs
- TBD-1: ...

### Change Notes
- What was unclear in the original text
- How ambiguity was removed
- Which terms were quantified