tech-spec

Plan and execute iterative technical interviews to produce a complete Tech Spec document.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/DiegoBulhoes/claude --skill tech-spec-diegobulhoes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-spec
Source: https://github.com/DiegoBulhoes/claude/tree/main/skills/workflow/tech-spec
Command: npx skills add https://github.com/DiegoBulhoes/claude --skill tech-spec-diegobulhoes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle to align on complex architecture and produce comprehensive technical specifications that guide delivery.

Core Features & Use Cases

  • Facilitates an iterative interview process that yields a complete Tech Spec document.
  • Covers architecture decisions, data models, security considerations, cost estimates, and rollout planning.
  • Useful for staff/principal engineer-level architecture reviews, ADRs, and pipeline governance.

Quick Start

Start the iterative tech-spec interview by outlining the problem and scope, then answer the guided questions to generate a complete Tech Spec.

Frequently Asked Questions about tech-spec

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

FAQPage Schema
How do I write a complete tech spec for distributed systems architecture?

To write a tech spec for distributed systems, an iterative interview process extracts architecture decisions, data models, and rollout plans to produce a comprehensive technical specification document.

How does the iterative technical interview process work for architecture reviews?

The iterative technical interview process works by guiding you through scoped questions about your problem, progressively building a structured tech spec that captures architecture decisions, risks, and cost estimates.

Can I generate architecture decision records and risk logs for Kubernetes infrastructure?

Yes, you can generate architecture decision records and risk logs for Kubernetes infrastructure. The workflow captures security considerations, cost estimates, and decision logs tailored to cloud infrastructure contexts.

What is the best way to document security considerations and cost estimates for a new architecture?

The best way to document security considerations and cost estimates is using a structured tech spec template driven by an interactive interview, ensuring all critical architectural metadata is captured systematically.

Does this tech spec workflow support PRD-driven development contexts?

Yes, the tech spec workflow supports PRD-driven development contexts. It is adaptable to both standalone architecture reviews and product requirement document-driven engineering pipelines.

What should a staff engineer include in a technical specification for cloud infrastructure?

A staff engineer should include architecture decisions, data models, observability metrics, security considerations, rollout plans, and a decision log in a technical specification for cloud infrastructure.