gstack-openclaw-office-hours

Guide founders through structured office-hours phases to produce a design doc.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-openclaw-office-hours-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/wodeh/gstack-kimi/tree/main/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-openclaw-office-hours-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides founders and builders through a structured office-hours session to ensure problem understanding before proposing solutions.

Core Features & Use Cases

  • Phase-based diagnostic workflow including Phase 1 Context Gathering, Phase 2 Startup/Builder modes, Phase 3 Premise Challenge, Phase 4 Alternatives, Phase 5 Design Doc, Phase 6 Closing.
  • Outputs a structured design document capturing problem statements, premises, approaches, and concrete next steps.
  • Enforces "One question at a time" prompting and explicit safeguards against premature implementation.

Quick Start

Provide a concise project brief and any existing docs, and I will guide you through phases 1–3 to craft a design doc.

Frequently Asked Questions about gstack-openclaw-office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured office hours session for evaluating startup ideas?

A structured office hours session evaluates startup ideas by guiding founders through context gathering, premise challenges, and design doc generation to ensure problem understanding before proposing solutions.

How do I run a product brainstorming session to validate a new product direction?

Run a product brainstorming session by progressing through six phases: context gathering, startup or builder mode selection, premise challenge, alternative exploration, design doc creation, and closing.

What's the best way to create a design doc for an unvalidated product idea?

Create a design doc by challenging premises and evaluating alternatives during office hours, capturing the problem statement, approaches, and concrete next steps without writing any code.

Can I use this office hours workflow for both startup diagnostics and side project brainstorming?

Yes, the office hours workflow supports both contexts by selecting Builder mode for side projects or Startup mode for ventures during Phase 2, tailoring the diagnostic questions accordingly.

Does this product direction evaluation process write code or just output documentation?

The product direction evaluation process explicitly safeguards against premature implementation and never writes code, focusing entirely on producing a structured design document with concrete next steps.