<!-- owner: RStack developed by Richardson Gunde -->

# Documentation Standards Skill

## Document Types

### BRD (Business Requirements Document)
- Audience: C-level executives, business stakeholders
- Tone: Non-technical, outcome-focused
- Must include: Executive summary, business objectives, KPIs, scope

### FRD (Functional Requirements Document)
- Audience: Development team, QA engineers
- Tone: Technical, precise
- Must include: Detailed FRs/NFRs, data models, acceptance criteria

### SOW (Statement of Work)
- Audience: Client and vendor leadership
- Tone: Formal, contractual
- Must include: Deliverables, timeline, team structure, sign-off placeholders

## Writing Rules
- Use numbered sections and tables for clarity
- Acceptance criteria must be testable
- No vague terms ("fast", "user-friendly") — use measurable targets
- Include version number and date on all documents
- Cross-reference requirement IDs consistently