What problem does it solve? Writing technical design documents that are complete, standalone, and readable is hard: drafts often assume hidden conversation context, bury decisions in walls of prose, or omit validation guidance. This Skill produces a full design document in one pass that any reader can understand without the original discussion. ## Core Features & Use Cases - One-pass document generation: Gathers only the scope that matters, asks material clarifying questions up front, then writes the complete document without section-by-section approval cycles. - ADHD-optimized structure: Enforces short orienting paragraphs, liberal bulleted lists, frequent fenced code examples, inline term definitions, and prominent related-information links so readers can scan and resume easily. - Cold-reader validation: Runs a fresh sub-agent comprehension test to flag jargon, ordering problems, and missing context before delivery. - Use Case: Ask for an RFC describing a new caching layer; receive a standalone Markdown document covering the problem, proposed design, concrete mechanics, migration behavior, and a final Manual QA section. ## Quick Start Write a technical design document for adding rate limiting to our public API, including the proposed design, failure handling, and a Manual QA section.
