technical-design-doc-creator

Generates structured Technical Design Documents through interactive discovery with mandatory and optional sections.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill technical-design-doc-creator-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-design-doc-creator
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28creation%29/create-technical-design-doc
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill technical-design-doc-creator-peterson-benhame

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Technical Design Document from scratch is time-consuming and often results in inconsistent, incomplete specs that miss critical sections like security, monitoring, or rollback plans. This Skill guides an AI agent through an interactive discovery process to produce a complete, standards-based TDD before implementation begins. ## Core Features & Use Cases - Interactive Discovery Workflow: The agent asks structured questions about project name, size, type, problem statement, scope, and technical approach before generating the document. - Adaptive Section Enforcement: Mandatory sections (Context, Problem Statement, Scope, Technical Solution, Risks, Implementation Plan) cannot be skipped, while Security, Monitoring, and Rollback become mandatory for payment, auth, or production systems. - Multi-Language Output: Automatically generates the TDD in English, Portuguese, or Spanish based on the language of the user's request. - Use Case: Ask the agent to create a TDD for a Stripe payment integration, and it will gather requirements, enforce the PCI DSS security section, and produce a full document with architecture diagrams, API contracts, risk matrix, testing strategy, and rollback plan. ## Quick Start Ask the agent to create a TDD for your project, for example by saying: create a TDD for integrating Stripe payments into our subscription system.

Frequently Asked Questions about technical-design-doc-creator

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

FAQPage Schema
How do I create a technical design document with an AI agent?

Ask the agent to create a TDD for your project, such as a feature or integration. The skill runs an interactive workflow that asks about project size, type, problem statement, scope, and technical approach, then generates a complete Markdown document with all required sections.

What sections should a technical design document include?

A TDD should include context, problem statement, scope, technical solution, risks, and an implementation plan as mandatory sections. For payment, auth, or production systems, security considerations, monitoring and observability, and a rollback plan are also mandatory.

Can I generate a design doc in Portuguese or Spanish?

Yes, the skill detects the language of your request and generates the entire TDD, including section headers and prose, in English, Portuguese, or Spanish. Technical terms like API, webhook, and rollback remain in English where appropriate.

When should I not use a technical design document?

Skip a TDD for bug fixes, minor refactors without architectural changes, documentation updates, and simple configuration changes. The skill is designed for features, integrations, migrations, and infrastructure work that require team alignment before implementation.

Why does the agent keep asking questions before writing the design doc?

The skill enforces mandatory sections and will not finalize the document until it has the problem statement, scope, technical approach, risks, and implementation plan. For payment or auth projects it also insists on security details such as encryption, PII handling, and compliance requirements.