Design Doc

Turns technical feature requests into proper design docs with all the sections engineers actually need: context, constraints, implementation outline, acceptance criteria, and testing approach. Uses Setext-style markdown headers and pushes you to be specific about behavior, like "max 100 chars" instead of vague handwaving. The workflow is straightforward: gather context, fill out the template, make sure your acceptance criteria are testable. Worth having if you're tired of design docs that skip error handling or forget to define what "done" means. The emphasis on non-goals is smart, helps keep scope creep in check before you start building.