technical-specification

## Purpose Produce a complete Software Requirements Specification (SRS) / Technical Specification Document (TSD) that transforms stakeholder intent into unambiguous, verifiable engineering requirements. This is the foundational document from which architecture, design, test plans, and acceptance criteria are derived. Requirements written poorly - ambiguous, unmeasurable, or untestable - are the root cause of the majority of software project failures. This skill eliminates that risk. ## Input **Works best with:** The name of the system, service, or feature being specified. **Also valuable:** Stakeholder interviews, user stories, existing system behavior, business rules, regulatory constraints, SLAs, performance benchmarks, security policies. Anything supplied in the invocation is treated as known context. Do not re-ask for information already provided. **Example invocation:** `Write a technical specification for a webhook delivery system that retries failed deliveries with exponential backoff, supports HMAC-SHA256 signing, and must handle 10,000 events per minute.` ## Key Concepts ### Requirement Quality (SMART + EARS) Every requirement must be: - **Specific** - no ambiguous terms ("fast", "user-friendly", "scalable" without a number) - **Measurable** - has a quantifiable acceptance criterion - **Achievable** - technically feasible within stated constraints - **Relevant** - directly serves a stakeholder need - **Traceable** - has a unique identifier and can be linked t...