Tech Spec Writer
Converts high-level architecture into detailed, human-readable Technical Specifications. The bridge between Architect and Developers.
Install
npx skills add ydnikolaev/antigravity-factory --skill tech-spec-writergit clone --depth 1 https://github.com/ydnikolaev/antigravity-factory.git /tmp/antigravity-factory
mkdir -p ~/.claude/skills
cp -r /tmp/antigravity-factory/src/skills/tech-spec-writer ~/.claude/skills/tech-spec-writerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tech Spec Writer
> **MODE**: SPECIFICATION. You translate architecture into implementation blueprints.
> - READ architecture docs first
> - OUTPUT detailed specs in natural language
> - DO NOT write code
> [!IMPORTANT]
> ## First Step: Read Project Config & MCP
> Before making decisions, **always check**:
>
> | File | Purpose |
> |------|---------|
> | `project/CONFIG.yaml` | Stack versions, modules, architecture |
> | `mcp.yaml` | Project MCP server config |
> | `project/docs/active/architecture/*` | Context Map, API Contracts |
## Purpose
You are the **translator** between `@bmad-architect` and developers.
Your output is for **HUMANS**, not machines. The user will review your specs before developers start coding.
## When to Activate
- After `@bmad-architect` completes Context Map and API Contracts
- Before any coding skill starts implementation
- When user asks "What exactly will be built?"
**Anti-pattern**: Do NOT write actual code. That is the developer's job.
## Decision Tree
1. **IF** architecture docs exist (`project/docs/active/architecture/context-map.md`):
- Proceed to specification writing
2. **IF** architecture is incomplete:
- Return to `@bmad-architect` with specific questions
3. **ELSE**:
- Ask user for clarification
## Workflow
### Phase 1: Read Architecture
1. Read `project/docs/active/architecture/context-map.md`
2. Read `specs/backend-api.yaml` (if exists)
3. Identify Test Boundaries from Architect's notesDetails
- Skill name
tech-spec-writer- Repository
- ydnikolaev/antigravity-factory
- Path
src/skills/tech-spec-writer/SKILL.md- Repo updated
- 28 January 2026
FAQ
What does the Tech Spec Writer skill do?
Converts high-level architecture into detailed, human-readable Technical Specifications. The bridge between Architect and Developers.
How do I install the Tech Spec Writer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ydnikolaev/antigravity-factory --skill tech-spec-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tech Spec Writer popular?
It lives in ydnikolaev/antigravity-factory, which has 9 GitHub stars and 2 forks.
Related skills
Backend Go Expert
9ydnikolaev/antigravity-factory
Expert Go developer (1.25+) specializing in Clean Architecture and DDD.
Bmad Architect
9ydnikolaev/antigravity-factory
The Lead Architect for Antigravity TMA projects. Enforces DDD, BMAD V6, and coordinates the squad.
CLI Architect
9ydnikolaev/antigravity-factory
Expert in Go CLI Architecture (Cobra, Viper, POSIX).
Archviz Storyboard
5felipealmeidasid/Pack-skills-for-archviz
Create professional architectural visualization storyboards, project storyboard packages, moodboards, architectural detail boards, film-sequence boards, clean keyframe plans, GPT Image board prompts, and Seedance video prompt packages for real estate presentations. Use when the user provides archviz renders, photos, floor plans, real estate assets, approved images, or a create-real-estate-worlds handoff and wants cinematic storyboard boards with strict architectural fidelity. Default project formats are 9:16 for Reels/social and 16:9 for presentations/horizontal films; ask the aspect ratio at
Project Bro
9ydnikolaev/antigravity-factory
Your project awareness buddy. Knows current state, reads docs, analyzes code, answers "where are we?" questions. Activate with "bro" or "project-bro".
Grantproof
5ellewangyuan/grantproof
Surfaces common writing-style mistakes in federal R&D grant prose — NSF SBIR/STTR, DoD SBIR, NIH SBIR, DOE, DARPA, NASA, NOAA, and similar. For each mistake, identifies where the issue is, explains why reviewers downgrade it, and shows a sample rewrite structure the founder can apply. Use when the user pastes draft writing for an R&D grant pitch or proposal.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.