SKILL FILE

Technical Spec Writer with AI

Write technical specifications with architecture, data models, and API designs — bridge the PRD-to-engineering gap for backend and infrastructure features.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Architecture overview

High-level diagram + description: which systems are involved, how they connect, what changes.

2

Data models

New tables / fields / relationships. Migration considerations. Indexes worth flagging.

3

API contracts

Endpoints, request / response shapes, error cases, authentication.

4

Failure modes

What can go wrong, how the system degrades, what gets retried vs surfaced.

5

Migration plan

If existing data needs to move or transform, the steps + rollback plan.

6

Open technical questions

What needs an engineer to decide vs what the PM can specify.

What you can build with this

Backend feature ready to scope

PRD approved, now generate the tech spec so engineering can scope and start.

API design

New endpoint or breaking change to existing one — spec it before building.

Data migration

Schema change, table merge, field rename — write the migration plan up front.

PM-engineering pair

Co-write with a senior engineer. PM owns the product intent, eng owns the technical detail.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

Usually co-written. The PM owns the product intent + acceptance criteria; the engineer owns the architecture decisions. The skill is built so a PM can write a first draft an engineer reviews — not the other way around.
PRD = what we're building and why, from the user's perspective. Tech spec = how it's built, from the system's perspective. The tech spec sits downstream of the PRD.
You need to understand systems conceptually (databases, APIs, services) but you don't need to write code. The skill structures the thinking; engineering reviews the technical specifics.
4–10 pages for medium features. Shorter for self-contained API changes; longer for cross-system architecture.
Anything that touches data persistence, API contracts, or cross-service boundaries — yes. Single-service refactors or bug fixes — usually no.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →