technical-design-doc-creator

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).

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/skills/(creation)/create-technical-design-doc/SKILL.md

Quality

Content

45%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and workflow-driven with strong validation gating, but it is severely over-long and monolithic: every template and bilingual variant is inlined rather than split into referenced files. Conciseness and progressive disclosure are the clear weak points.

Suggestions

Move the 20 section templates into a single references file (e.g. references/section-templates.md) and keep SKILL.md as an overview with one-level-deep links, to fix progressive disclosure and cut body length.

Extract the EN/PT/ES translation tables and bilingual prompt examples into a separate references/translations.md rather than inlining all three languages.

Trim the 'Industry Standards Reference', 'Common Anti-Patterns', and 'Important Notes' sections, which restate widely known concepts (Google design docs, OWASP, GDPR) Claude already understands.

Dimension	Reasoning	Score
Conciseness	The body is ~1480 lines and noticeably verbose, inlining full bilingual (EN/PT/ES) template tables, all 20 section templates, emoji-decorated examples, and 'Important Notes' restating concepts Claude already knows; significant padding could be moved out or trimmed.	2 / 5
Actionability	Provides concrete document templates, AskQuestion JSON payloads, and example prompts, but the core guidance is abstract template-filling and 'ask the user in their language' loops rather than copy-paste executable instructions, with key details left as placeholders.	3 / 5
Workflow Clarity	A clear 6-step interactive workflow is sequenced with explicit validation checkpoints (mandatory/critical section checklists, per-project-type gating) and feedback loops for missing sections, with only minor gaps in error-recovery detail.	4 / 5
Progressive Disclosure	Monolithic single file with no bundle files in references/scripts/assets; the 20 full section templates and translation tables are inlined content that clearly belongs in separate referenced files, with no one-level-deep reference structure.	2 / 5
	Total	11 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is excellent: it specifies concrete capabilities, includes abundant natural trigger phrases, answers both what and when explicitly, and actively distinguishes itself from sibling skills. It uses third person and concisely covers the domain without fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery' — covering creation, sectioning, and interactive gathering, comprehensive for the domain.	5 / 5
Completeness	Explicitly answers both what (creates TDDs with mandatory/optional sections via interactive discovery) and when ('Use when user asks to...'), plus explicit exclusions ('Do NOT use for README files, API docs').	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms ('write a design doc', 'create a TDD', 'technical spec', 'architecture document', 'RFC', 'design proposal') that users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (technical design docs) with explicit conflict avoidance ('Do NOT use for README files, API docs, or general documentation (use docs-writer instead)'), minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1485 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: tech-leads-club/agent-skills
Path: packages/skills-catalog/skills/(creation)/create-technical-design-doc/SKILL.md
Commit: fe318be

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.