technical-spec-template

# Technical Spec Template Skill Write technical specifications that engineers actually read — clear problem framing, unambiguous requirements, explicit decisions, and documented trade-offs. ## Required Inputs Ask the user for these if not provided: - **Feature or system description** (what needs to be specced) - **Related PRD or product brief** (if available) - **Engineering reviewers** (whose sign-off is needed) - **Known constraints** (technical limitations, security requirements, performance targets) ## When to Write a Tech Spec Write a tech spec when: - The feature requires changes to 2+ systems - There are significant architectural decisions to make - More than one engineer will work on the implementation - The feature has security, privacy, or compliance implications - Estimated effort is >5 story points Skip the spec for trivial bug fixes or 1-2 hour changes. --- ## Technical Spec Output Format ### Technical Specification — [Feature Name] **Author:** [Name] **Status:** Draft | In Review | Approved | Implemented **Created:** [Date] | **Last Updated:** [Date] **Reviewers:** [Eng Lead, Architect, PM, Security if needed] **Related PRD:** [Link] | **Jira Epic:** [Link] --- #### 1. Problem Statement > [2–3 sentences. What problem are we solving and why now? No solution language here.] #### 2. Goals & Non-Goals **Goals (in scope):** - [Specific, measurable outcome] - [Specific, measurable outcome] **Non-Goals (explicitly out of scope):** - [What this spec does ...