Technical Requirements (SRS)

Draft software requirements based on an approved BRD. Covers architecture, interfaces, data, NFRs, security, compliance, and rollout — each section drafted with your approval.

Announce at start: "I'm using the technical-requirements skill to draft an SRS based on the approved BRD."

When to use

• "write an SRS", "technical spec", "architecture doc", "engineering requirements"
• After business-requirements skill completes

Prerequisites

Reads docs/requirements/brd.md on start. If no BRD exists, suggest running business-requirements first.

Phases

flowchart TD
    P1[Architecture] --> P2[Interfaces & Data]
    P2 --> P3[Non-functional]
    P3 -->|auto-bump| P4[Security & Privacy]
    P4 --> P5[Compliance]
    P5 --> P6
    P3 -->|no signals| P6[Rollout & Rollback]
    P6 --> P7[SRS Sign-off]
    P7 --> P8[Dual-voice SRS Review]
    P8 --> DONE[Done → suggest red-team]

Architecture

Interview using roles/tech-lead.md. Reference references/google-design-doc-patterns.md. Draft:

• SRS §Architecture — main components, how they relate

Interfaces & Data

Interview using roles/tech-lead.md. Draft:

• SRS §Interfaces — APIs, contracts, versioning strategy
• SRS §Data — data model, storage, retention, classification

Non-functional

Interview using roles/tech-lead.md, roles/sre.md, roles/qa.md, roles/security-legal.md*. Draft:

• SRS §SLOs — numeric targets, always
• SRS §Security — threat model sketch
• SRS §Privacy — data classification
• SRS §Observability — logs, metrics, traces, alerts
• SRS §Testability — what must be testable, test surfaces

*security-legal if auto-bump signals detected

Security & Privacy (auto-bump only)

Triggered when state.md has auto-bump signals. Interview using roles/security-legal.md. Draft:

• Deep threat model, data classification, encryption, audit trail
• Added to SRS §Security and §Privacy sections

Compliance (auto-bump only)

Interview using roles/security-legal.md. Draft:

• Applicable regulations, evidence requirements, DPA status
• Added to SRS §Compliance section

Rollout & Rollback

Interview using roles/sre.md. Draft:

• SRS §Rollout — staged? feature-flagged? percentages and durations
• SRS §Rollback — explicit abort criteria

SRS Sign-off

Present full SRS. List all [ASSUMPTION] and [OPEN] items. Ask for sign-off.

Dual-voice SRS Review

Dispatch sub-agents/dual-voice-reviewer.md for independent second opinion on architecture and NFRs. Present findings.

Preset Weighting

Section	greenfield	feature	internal
§integration	light	heavy	medium
§migration-compat	skip	required	required
§api-versioning	medium	medium	heavy
§deprecation	optional	required	required

Four-Beat Rhythm

Same as business-requirements: Orient → Work → Present → Approve → Commit. One section at a time, no silent writes.

Tone

• Engineering-precise. No vague "it should be fast" — give numbers.
• Every decision gets an alternatives-considered entry in decisions.md.
• Reference references/hyrum-law-checklist.md when reviewing interfaces.

Next step

"SRS complete. Ready for adversarial review? Say 'red-team this' to continue."