skills.rest
servitola
servitolaCOMMUNITY
Explore all skills by this author →
GitHub

tech-spec-planning

Generate a formal tech-spec.md from a user-spec.md and project knowledge.

12|2|Updated Feb 2, 2020
Search Tags:#planning#architecture#documentation#requirements#engineering#process#tech-spec
One-click install
npx skills add https://github.com/servitola/dotfiles --skill tech-spec-planning-servitola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-spec-planning
Source: https://github.com/servitola/dotfiles/tree/main/claude-code/skills/tech-spec-planning
Command: npx skills add https://github.com/servitola/dotfiles --skill tech-spec-planning-servitola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates a structured, architecture-focused technical specification document starting from an existing user-spec.md and project knowledge references, reducing ambiguity and accelerating alignment between product and engineering teams.

Core Features & Use Cases

  • Generate a complete tech-spec.md including architecture, decisions, testing strategy, and an implementation plan.
  • Ingest input from work/{feature}/user-spec.md and references in .claude/skills/project-knowledge/references/ to ensure alignment with project context.
  • Provide phase-based content with checkpoints, traceability, and review-ready outputs for approval.
  • Use Case: When starting a new feature, draft a tech-spec for engineering and product review.

Quick Start

Provide the feature name and ensure work/{feature}/user-spec.md exists to begin drafting the tech-spec

Frequently Asked Questions about tech-spec-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a technical specification document from existing requirements?▼

To draft a technical specification, this Skill ingests your existing user-spec.md and project references to generate a formal tech-spec document covering architecture decisions, testing strategy, and implementation planning.

What is included in a complete tech spec for feature development?▼

A complete tech spec includes phase-driven content with checkpoints, architecture decisions, a testing strategy, an implementation plan, and traceable outputs ready for engineering and product team review.

How do I generate a tech spec that aligns with my project's existing architecture?▼

You generate an aligned tech spec by loading existing project knowledge references from your .claude/skills directory alongside your feature's user-spec.md to ensure the output matches your established architectural context.

Do I need a user-spec.md file before starting tech spec planning?▼

Yes, you need an existing user-spec.md file located in your work/{feature}/ directory to provide the initial requirements before this Skill can draft the formal technical specification.

Can I use this for coordinating architecture decisions between product and engineering teams?▼

Yes, you can use the generated tech spec to coordinate architecture decisions by providing review-ready outputs with traceability that reduce ambiguity and accelerate alignment between product and engineering teams.

What's the best way to structure a tech spec for engineering review and approval?▼

The best way to structure a tech spec for approval is using phase-based content with checkpoints, ensuring frontmatter setup is correct and all outputs are traceable from requirements through validation plans.

Related Skills

Explore More Software Engineering Skills→
GenerativeAgentsGenerativeAgents

prd-writing

Generate a review-ready PRD from initial-requirements.md using the PRD template.

Official
Advanced
pradeepmoulipradeepmouli
2

speckit-plan

Convert feature specifications into structured plan.md technical designs.

Community
Advanced
jinlulijinluli

unity-adr

Create and compare architecture decision records within Unity projects.

Community
Intermediate
bybren-llcbybren-llc
395

confluence-docs

Create standardized ADR, runbook, and architecture documentation templates.

Official
Intermediate