skills.rest
Avila-Tek
Avila-TekOFFICIAL
Explore all skills by this author →
Website𝕏@avilatekdevGitHub

technical-design-document

Generate a Technical Design Document from a Spec Funcional and domain document.

Updated Mar 11, 2026
Search Tags:#tdd#architecture#documentation#technical-design#domain-model#spec-functional
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill technical-design-document-avila-tek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-design-document
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/planning-3-technical-design-document
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill technical-design-document-avila-tek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates precise Technical Design Documents (TDD) from a Spec Funcional and domain document, reducing manual drafting and ensuring architecture alignment.

Core Features & Use Cases

  • From a Spec Funcional and domain model, generate a structured TDD that documents architecture, data model, APIs, security, and integrations.
  • Outputs to the canonical TDD location for an epic (docs/epics/E-XXX_<slug>/tdd.md) and supports optional .docx export when requested.

Quick Start

Provide a Spec Funcional and the domain model, then request TDD generation for the related epic.

Frequently Asked Questions about technical-design-document

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

FAQPage Schema
How do I generate a technical design document from a functional spec?▼

To generate a technical design document from a functional spec, provide the spec and your domain model to automate TDD creation. The output covers architecture, data models, APIs, security, and integrations, strictly mapping one TDD per epic.

What is the 1:1 epic-to-TDD relationship in software architecture?▼

The 1:1 epic-to-TDD relationship ensures each epic receives its own dedicated technical design document. This mapping maintains architecture alignment by generating a unique TDD file at docs/epics/E-XXX_<slug>/tdd.md for every individual epic.

Can I export a TDD to .docx from a domain model and spec functional?▼

Yes, you can export a TDD to .docx from a domain model and spec functional. The system outputs the architecture documentation natively as a markdown file, with optional .docx export available upon request.

What do I need to create a production-ready TDD for an epic?▼

To create a production-ready TDD for an epic, you need a spec functional and an existing domain model. The system reads this planning context to output a structured document covering architecture, data models, APIs, security, and integrations.

Does this TDD generation process cover security and API integrations?▼

Yes, the TDD generation process covers security and API integrations. By reading the planning context and domain model, it produces a comprehensive technical design document that explicitly details architecture, data models, APIs, security protocols, and integrations.

Related Skills

Explore More Software Engineering Skills→
dandudzidandudzi
2

ddd-strategic-design

Map business domains and define bounded contexts with DDD strategic patterns.

Community
Advanced
jctannerjctanner

generate-architecture-diagrams

Generate Mermaid, C4, ASCII, and PNG architecture diagrams from documentation.

Community
Advanced
AvihusittonAvihusitton

domain-driven-design

Assess DDD viability and generate strategic design artifacts for complex business software.

Community
Intermediate
bacocobacoco
67

bmad-architecture

Translate approved product requirements into structured architecture design documents.

Community
Intermediate