design-doc

To turn a rough idea into a structured design document, the Skill uses iterative clarification to ask targeted questions, logs the Q&A, and conducts research to generate review-ready proposals with trade-off analysis.

Writing an RFC with multiple architecture proposals is best handled by generating a baseline "Do nothing" option alongside at least two alternative solutions, automatically analyzing benefits, trade-offs, and consensus for each.

Yes, you can use prompt-driven development to gather requirements for technical proposals by asking one question at a time, waiting for complete user responses, and logging the idea-honing Q&A before proceeding.

Yes, the design doc generation process saves artifacts to a project directory like .design-docs/[slug] and formats the final output specifically for Google Docs compatibility.

Iterative clarification for an architecture decision record works by asking a single question at a time, waiting for complete user responses, and logging the Q&A to hone the initial rough idea before conducting targeted research.

A comprehensive design document for trade-off analysis should include a Proposal 0 "Do nothing" baseline, at least two alternative proposals, documented benefits, trade-offs, research findings, and a consensus tracking section.