Menu

Individual skill

design-doc

0upvotes

Write the technical design document a team reviews before coding, plus its ADR: current state, options with trade-offs, chosen approach, data and API changes, migration, rollback, risks, open questions, and who signs off. Use before code that touches a schema, a public contract, a shared module, or several services. `--spike` first investigates, time-boxed, a question the design cannot choose without; `--challenge` puts one agent per signing role on the draft; `--answer` records answers to its open questions. Triggers on: "design doc", "technical design", "tech design", "thiết kế kỹ thuật", "tài liệu thiết kế", "ADR", "architecture decision", "設計書", "detail design", "how should we build this", "technical spike", "spike this", "nghiên cứu kỹ thuật", "spike kỹ thuật", "技術調査", "スパイク", "pressure-test this design", "phản biện thiết kế", "設計の懸念を洗い出して", "finish the draft design", "viết tiếp thiết kế nháp", "設計書の下書きの続き", "record the design answers", "ghi câu trả lời vào thiết kế", "設計の回答を反映", "/atk:design-doc".

plugins/atk/skills/design-doc/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Technical Design Document (`atk:design-doc`)

Produces the document a Tech Lead and peers can review without a meeting, and the ADR that survives
the people who wrote it. The point is the comparison: a design with only one option is a plan, not a
design, and gets reviewed as such.

## Scope

Handles: describing the current implementation with citations, framing the problem, comparing viable
options against stated criteria, specifying the chosen data model, API contracts, and the migration
and rollout sequence the change requires, and writing the ADR entry. Under `--spike`, it also
investigates a question the comparison cannot be scored without, inside a time box somebody set,
and writes what was found instead of a design. Given a design at `DRAFT`, it finishes or revises it.
Under `--answer`, it records a person's answers to a design's open questions, and the edits review
Back to top