gstack-openclaw-office-hours

To turn a product idea into a structured design doc, use a phase-driven, one-question-at-a-time discovery process. This approach elicits precise problem statements and user needs, culminating in a complete design document with defined premises and recommended approaches.

A YC-style office hours session for product design is a structured discovery process that guides teams to deeply understand a problem before proposing solutions. It uses a phase-based workflow to articulate problem statements, demand evidence, and success criteria.

Write a design document with clear premises by following a six-phase discovery workflow that sequentially prompts for specific inputs. The resulting document automatically organizes premises, approaches considered, open questions, and next steps into a structured format.

Yes, you can use this phase-based workflow for both startup and builder modes. It applies the same six-phase, one-question-at-a-time discovery process to generate design documents, ensuring alignment and tracking session signals regardless of the mode.

No, this design doc generation process does not write code or implementation logic. It strictly enforces design-doc content requirements and avoids any code generation actions, focusing entirely on problem discovery and structured design documentation.

Design iterations are tracked during office hours by monitoring session signals throughout the phase-based workflow. These observed signals are summarized and included in the final design document, which is saved to memory for continuity across future discussions.