Generate Comprehensive Technical Specifications

This skill creates comprehensive, well-structured technical specification documents that serve as definitive blueprints for software development, translating complex requirements into clear, actionable specs for development teams, architects, and stakeholders. It follows a hierarchical document structure: Executive Summary (project overview, objectives, timeline), System Overview (architecture diagram, component relationships, tech stack decisions), Detailed Requirements (functional, non-functional, constraints/assumptions), Technical Design (architecture components, data models, API specifications, security considerations), and Implementation Plan (development phases, dependencies/risks, testing strategy).

Use it when writing a technical specification document for a software project or system design that needs to guide implementation across a development team and stakeholders.

Requirements are documented with MoSCoW prioritization (Must/Should/Could/Won't) using a fixed template: a unique FR/NFR-XXX ID, priority, description, acceptance criteria, dependencies, and effort estimation in story points - illustrated by a worked FR-001 example specifying OAuth 2.0 authentication with Google/GitHub/Microsoft SSO, a 24-hour session timeout, and account lockout after 5 failed attempts. API specifications follow OpenAPI 3.0 format with request/response schemas, validation rules, and example values, plus documented error handling, rate limiting, and authentication requirements per endpoint. Data models are documented with entity-relationship diagrams and detailed SQL schema definitions covering constraints (e.g. a regex-validated email check) and indexing strategy with performance implications. Architecture Decision Records (ADRs) capture major technical decisions with status, date, deciders, context, decision, rationale, and consequences (positive, negative, risks) - illustrated by a worked example choosing PostgreSQL 15+ with read replicas over alternatives, reasoning from ACID compliance, JSON support, proven scalability, and tooling, while flagging write-scaling as a sharding risk. Security and compliance specifications cover authentication/authorization (JWT signing algorithm, token expiration windows, RBAC), data protection (encryption at rest and in transit, PII pseudonymization), and named compliance standards (GDPR right-to-deletion and data portability, SOC 2 Type II audit logging, PCI DSS for payment data). Implementation timelines break work into phases with deliverables, checkbox acceptance criteria, dependencies, and risk mitigation. Testing strategy spans unit tests (80%+ coverage on business logic), integration tests (API endpoints, database interactions), performance/load testing, security testing (penetration testing, vulnerability scanning), and user acceptance testing.

Recommends living-document maintenance practices: version-controlling all specifications, monthly review cycles, stakeholder sign-off processes, change-impact assessments, and automated documentation generation where possible.

Software architects, technical leads, and product/engineering teams who need a complete, standardized specification document - requirements, API contracts, data models, ADRs, security specs, and a phased implementation plan - rather than an ad-hoc or incomplete design doc.