office-hours

To map startup requirements into a design doc, this Skill uses a phase-driven workflow starting with Context Gathering to crystallize ideas and surface risks without writing code. It enforces completeness principles to ensure you understand the problem space before solutioning.

The best way to run a product planning workshop is using structured phase-based interviewing. This Skill guides startup and builder modes through Premise Challenge and Alternatives phases to produce a formal plan report with a risk and completeness assessment.

Yes, you can use phase management to brainstorm product ideas without generating code. The Skill provides a Builder Brainstorm phase and structured prompts that yield design-doc style outputs and escalation prompts, strictly avoiding code generation.

Yes, this design planning tool supports YAML frontmatter-driven metadata. It uses this structured metadata alongside a rigid AskUserQuestion protocol to guide the phase-based interviewing process and log telemetry.

To challenge project premises during early-stage product design, the Skill implements a dedicated Premise Challenge phase. This step questions your initial assumptions before moving to alternatives evaluation and final plan generation.

A limitation of using structured interviewing for startup design docs is the rigid adherence to the AskUserQuestion protocol and phase progression. Users cannot skip the Context Gathering or diagnostic phases to jump directly to solutioning or writing code.