gstack-office-hours

To gather context for a startup design discussion, use a phase-driven diagnostic workflow that maps project goals, codebase context, and the docs landscape. This enforces structured context-gathering to align the team before solution design.

The best way to structure YC-style office hours is applying a diagnostic framework with the six forcing questions to push for concrete details. This phase-driven process outputs a design doc and a concrete plan for next actions.

Run a diagnostic session by loading your CLAUDE.md and TODOS.md files, then outlining the goal and current context. The workflow maps your codebase context and design landscape to decide the mode and next steps.

Yes, you can use the diagnostic workflow for both startup mode and builder mode. Startup mode focuses on problem discovery and finding a wedge, while builder mode handles design thinking brainstorming.

To start a design-first discussion for builders, you need your CLAUDE.md and TODOS.md files loaded. Outline your session goal and current context to initiate Phase 1 context gathering.

From a phase-driven startup diagnostic workflow, you should expect a design doc and a concrete plan for next actions. It maps your goals and docs landscape to decide the mode and subsequent steps.