skills.rest
speqqai
speqqaiOFFICIAL
Explore all skills by this author →
GitHub

tech-design-doc

Translate PRD requirements into traceable technical design documents with ASCII architecture.

Updated Apr 27, 2026
Search Tags:#design#tdd#architecture#documentation#prd#ascii-diagram
One-click install
npx skills add https://github.com/speqqai/claude --skill tech-design-doc-speqqai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-design-doc
Source: https://github.com/speqqai/claude/tree/main/skills/tech-design-doc
Command: npx skills add https://github.com/speqqai/claude --skill tech-design-doc-speqqai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical Design Documents (TDDs) that translate PRD requirements into architecture decisions, ensuring zero custom code, traceability, and SDK-first design.

Core Features & Use Cases

  • Enforces mandatory TDD structure using references/tdd-template.md and references/tdd-standard.md.
  • Ensures PRD-to-design traceability with requirement IDs.
  • ASCII architecture diagram, server-side design, and documentation references.
  • Zero custom code policy with explicit gap documentation when a capability is missing.

Quick Start

Load the approved PRD, reference the TDD templates, and draft the architecture decisions in the prescribed sections.

Frequently Asked Questions about tech-design-doc

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

FAQPage Schema
How do I translate PRD requirements into a technical design document?▼

You can translate PRD requirements into a technical design document by loading the approved PRD, referencing the TDD templates, and mapping each requirement ID to SDK or framework capabilities. This ensures full PRD-to-design traceability and architectural consistency.

What is a zero custom code policy in software architecture design?▼

A zero custom code policy in architecture design mandates mapping PRD requirements directly to existing SDK or framework capabilities. It enforces explicit gap documentation to justify any custom code written when a native capability is missing.

How do I ensure traceability between PRDs and TDD architecture decisions?▼

To ensure traceability between PRDs and TDDs, enforce a mandatory document structure that tags architecture decisions, API contracts, and security considerations with their originating PRD requirement IDs.

Does a TDD template need to include ASCII architecture diagrams?▼

Yes, a production-grade TDD template includes ASCII architecture diagrams to visualize server-side design. It also specifies API contracts and official documentation references to complete the architectural overview.

When should I document capability gaps in a technical design document?▼

You should document capability gaps in a technical design document whenever existing SDK or framework capabilities cannot fulfill a PRD requirement. This explicit gap documentation justifies the need for custom code under the zero custom code policy.

Related Skills

Explore More Software Engineering Skills→
heltondoriaheltondoria
1

feature-spec

Generate implementation specifications from PRD features with API contracts and test scenarios.

Community
Advanced
cc01cccc01cc
4

vscode-extension-official-api-reference

Guide VS Code extension development using official API references.

Community
Intermediate
malakhov-dmitriimalakhov-dmitrii

code-hygiene

Analyze codebases for dead code, test gaps, duplication, drift, and security issues.

Community
Advanced
compozycompozy
2.5k

cy-create-techspec

Generates a complete draft of TechSpec and companion documents from your uploaded files.

Official
Advanced