technical-design-doc-creator SKILL.md skillA
technical-design-doc-creator from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/technical-design-doc-creator@git:20260226.8dca459Pins git:20260226.8dca459 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(creation)/create-technical-design-doc/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260226.8dca459, committed Feb 26, 2026
- First version recorded
- Feb 5, 2026
- Size
- 52,020 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Technical Design Doc Creator You are an expert in creating Technical Design Documents (TDDs) that clearly communicate software architecture decisions, implementation plans, and risk assessments following industry best practices. ## When to Use This Skill Use this skill when: - User asks to "create a TDD", "write a design doc", or "document technical design" - User asks to "criar um TDD", "escrever um design doc", or "documentar design técnico" - Starting a new feature or integration project - Designing a system that requires team alignment - Planning a migration or replacement of existing systems - User mentions needing documentation for stakeholder approval - Before implementing significant technical changes ## Language Adaptation **CRITICAL**: Always generate the TDD in the **same language as the user's request**. Detect the language automatically from the user's input and generate all content (headers, prose, explanations) in that language. **Translation Guidelines**: - Translate all section headers, prose, and explanations to match user's language - Keep technical terms in English when appropriate (e.g., "API", "webhook", "JSON", "rollback", "feature flag") …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/technical-design-doc-creator@sha256:6e628b009e85276fThe line at the top of this page pins the label git:20260226.8dca459, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ywj7whb42m5qu2rp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Feb 5, 2026 and Feb 26, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260226.8dca459 latest | 2026-02-26 | 8dca459 | 52,020 B | A | view · diff |
| git:20260207.e3f6d8e | 2026-02-07 | e3f6d8e | 51,790 B | A | view · diff |
| git:20260205.905f8bb | 2026-02-05 | 905f8bb | 51,790 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (52020 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ywj7whb42m5qu2rp GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/technical-design-doc-creator GET https://markdownregistry.com/api/v1/blob/6e628b009e85276f8e7a63d1f323cc7ec5f7a02e261344c7df7f94e9ecfdb47b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.