tech-design

Provide your notes, issue, or PRD and the Skill compresses them into a polished TD while preserving intent. It asks 3-5 high-leverage questions only when missing information materially changes the design, and marks unknowns with [TODO: ...] placeholders.

Share the existing TD and the Skill acts as a senior reviewer, checking for unclear problems, hidden scope creep, weak alternatives, unsupported recommendations, and vague claims. Each issue gets a severity rating, an explanation of why it matters, and a suggested fix.

Yes, the markdown is written in a dialect Notion understands on paste. It uses only three heading levels, GFM pipe tables, checkbox syntax, fenced code blocks, and standard bold, italic, and links, avoiding raw HTML and footnotes.

Structure follows the content rather than a fixed template. Common sections are context, proposed solution, alternatives considered, recommendation, rollout, and open questions, while boilerplate like testing strategy, failure mode tables, and decision logs is omitted.

Skip sections or the entire formal structure when the change is trivially backward-compatible or the rollout is straightforward. The Skill deliberately omits boilerplate sections that add no decision-making value for senior readers.