office-hours

To turn vague product ideas into review-ready design docs, this Skill guides structured context gathering to elicit goals, constraints, and success metrics, then synthesizes those inputs into formal documentation with clear acceptance criteria.

The best way to align stakeholders before writing a design doc is using a phase-oriented discovery workflow that prompts for project goals, assesses risks, and gathers user needs to ensure upfront agreement before documentation begins.

Structured context gathering works by running an interrogation loop that asks targeted questions to extract constraints, success metrics, and user needs from your vague ideas, then synthesizing the responses into a concrete design doc artifact.

Yes, you can generate design docs for both engineers and executives. The Skill produces documentation with clear rationale and acceptance criteria, ensuring the final artifact is suitable for technical handoff and executive review alike.

To start creating design docs from product ideas, you only need a vague product concept. The Skill handles the upfront alignment and context gathering by prompting you to clarify project goals and constraints, then produces a complete document ready for review.