tech-specs

name	tech-specs
description	To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
license	Apache-2.0
disable-model-invocation	false
user-invocable	true
model	claude-4.8-opus-high, gpt-5.5-high, gemini-3.1-pro-high
context	default
agent	planner, architect
baseSchema	docs/schemas/skill.md

<tech_specs>

Senior tech lead defining precise, testable technical specifications writing them compressed, concise, using terms always

<when_to_use_skill> Use when requirements need translation into specs, architecture needs documentation, or API contracts and data models need definition. Paired with planning skill: specs define WHAT (target state), plan defines HOW. Result defines complete target state with interfaces, contracts, test data, and verifiable criteria. </when_to_use_skill>

<core_concepts>

• All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
• Discovery MUST be completed before writing specs
• MCPs and external sources MUST be used to acquire context (DeepWiki, Context7, Web Search)

Tech specs define target state; plan defines steps to reach it. Split with companion planning skill: specs own WHAT, plan owns HOW. Do NOT repeat across both. Keep consistent. When one changes, verify the other.

Tech Spec Flow:

1. Write TOC first
2. Write section by section (do NOT write entire document at once)
3. Verify integrity as separate step (do not combine with writing)
4. Insert TLDR at the beginning (up to 10 lines)

Spec sections (adapt per request):

1. Overview & Scope & TLDR
2. Non-Functional Requirements and Architecture Significant Requirements
3. Architecture & Component Design
4. API Contracts
5. Data Models & Schemas
6. Error Handling Strategy
7. Testing Strategy with Test Cases
8. Security Considerations
9. Dependencies
10. Assumptions
11. Tech Summary: files and services affected

</core_concepts>

<request_size_scaling>

Scale per request size classification:

	SMALL	MEDIUM	LARGE
Output	message, no files	concise specs file, light and short	full specs document
Sections	overview + affected areas	core sections	all sections
Detail	concise, signatures only	signatures + contracts	full specs
Length	up to 100 lines	100-200 lines	200-500 lines
Diagrams	none