Technical Specification

A tech spec answers how we'll build something — without over-prescribing implementation details that engineers should own. It bridges product requirements to engineering execution.

Step 1: Read the Requirements

Before writing, gather the inputs. A spec without requirements is guesswork.

Source	What to pull from it
PRD	Problem, goals, functional requirements, non-functional requirements, scope boundaries
Job stories	User workflows, acceptance criteria, edge cases
Conversation	If neither exists, interview the user to establish what the system must do and for whom

Flag anything ambiguous. A spec built on vague requirements produces vague engineering.

Step 2: Write the Spec

Use this structure. Adapt headings to the project — not every section applies every time.