Skip to main content
File: agents/sdlc/02-requirements.md · Model: Sonnet · Tools: Bash, Read, Write

Purpose

The requirements agent translates the transcript into precise, testable requirements. Every requirement has a specific, observable acceptance criterion that a QA engineer can test on day one.

Core principle

“The system should be fast” is not a requirement. “API p95 latency < 200ms under 1000 concurrent users, measured with k6” is.

What it does

  1. Reads transcript.json
  2. Extracts functional requirements (what the system must do)
  3. Extracts non-functional requirements (performance, security, scalability)
  4. Writes user stories with acceptance criteria
  5. Documents explicitly out-of-scope items
  6. Produces requirement_spec.json

Outputs