Tech Design Doc

Write or review a design doc, RFC or ADR with alternatives that could actually win, the tradeoff stated, and what would change the decision. Use for design docs or ADRs.

5 stars 1 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add eshmith7/claude-skills-library --skill tech-design-doc
Manual install
git clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/tech-skills/tech-design-doc ~/.claude/skills/tech-design-doc

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Design Doc and ADR

Most design documents describe the chosen solution, then add two alternatives afterwards so the section is not empty. Both are obviously worse, because they were written to lose. So the review adds nothing, the real tradeoff is never examined, and the decision gets relitigated in six months by somebody who cannot tell what was actually considered.

## When to use this

Trigger on: design doc, RFC, ADR, architecture decision record, technical proposal, tech spec, solution document, design review, "write up the design", "which approach should we take".

## Before you start

Required: the problem, and what you are considering doing about it.

Ask, briefly:
1. **The problem, stated without a solution inside it.** "We need a queue" is a solution. "Order confirmations are lost when the payment service is slow" is a problem. If it cannot be stated without naming the technology, the design is already decided and this document is a justification.
2. Constraints that are real: deadline, team size and skills, systems that cannot change, compliance, budget, who will operate it. A design that ignores who runs it is not a design.
3. **What you have already decided and will not reconsider.** Say it explicitly. A document pretending everything is open when it is not wastes the reviewers' time and their goodwill.
4. Scale now, and scale in a year. Both. Designing for the second without stating the first is the commonest source of over-engineering.
Read the full skill on GitHub

Details

Skill name
tech-design-doc
Path
tech-skills/tech-design-doc/SKILL.md
Repo updated
9 September 2026

FAQ

What does the Tech Design Doc skill do?

Write or review a design doc, RFC or ADR with alternatives that could actually win, the tradeoff stated, and what would change the decision. Use for design docs or ADRs.

How do I install the Tech Design Doc skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill tech-design-doc. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tech Design Doc popular?

It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.

Related skills

Content Brief

5

eshmith7/claude-skills-library

Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.

Writing & Content

Content Performance Audit

5

eshmith7/claude-skills-library

Turn a performance export into one decision per asset: keep, refresh, rewrite, consolidate or delete, with cannibalisation groups found first. Use for content audits or pruning.

Writing & Content

Content Prepublication Check

5

eshmith7/claude-skills-library

Check a draft before publishing: every claim registered with its source, numbers verified, headline against body, originality and compliance flags. Use before anything goes out.

Writing & Content

Deep Design

5

npow/claude-skills

The single entry point for ALL design and specification work. Use when designing, specifying, architecting, writing a spec, RFC, design doc, or drafting a design for any system, feature, product, protocol, game, or workflow. Trigger phrases include "design this", "architect this", "design spec", "design review", "write a spec", "technical spec", "RFC", "API design", "data model", and "implementation spec". Default mode: adversarial stress-testing with parallel critics. Use `--spec` for lightweight single-session spec document generation without critics.

Writing & Content

Student Answer Writing

5

eshmith7/claude-skills-library

Structure an answer around its command word and marks, then review your own attempt for content missing against content not credited. Use for answer writing or lost marks.

Writing & Content

Deep Idea

5

npow/claude-skills

Use when generating novel ideas, breakthroughs, concepts, product ideas, research directions, startup ideas, or creative angles in any domain that aren't already obvious. Trigger phrases include "give me ideas for", "novel ideas", "creative ideas", "brainstorm non-obvious ideas", "breakthrough ideas", "product concepts", "research directions", "startup ideas", "idea generation", "think outside the box on", "original ideas", "non-obvious ideas", "what could we build in", "fresh angles on". Forces structural extrapolation through orthogonal generation strategies, adversarial novelty killing, and

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.