gstack-openclaw-office-hours

Clarify product problems through structured office hours and produce design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structuring conversations to ensure the problem is understood before proposing solutions, delivering a clear design-focused output instead of code.

Core Features & Use Cases

  • Phase-based questioning that surfaces real user needs and constraints
  • Produces a formal design document (not code) to guide decisions
  • Works for startups, intrapreneurship projects, hackathons, open-source work, and learning sessions

Quick Start

Ask the user for their goal and confirm the problem before proposing any solution.

Frequently Asked Questions about gstack-openclaw-office-hours

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

FAQPage Schema
What is YC office hours style questioning for product management?▼

YC office hours style questioning is a structured conversation method that clarifies your product problem and desired outcome through phase-based inquiry before proposing any solutions. It forces clear product thinking by surfacing real user needs and constraints early.

How do I validate a startup idea without writing code?▼

You validate a startup idea without writing code by running it through structured office hours questioning to surface real constraints, then producing a formal design document to guide decisions instead of jumping straight into implementation.

Can I use this for open source projects and hackathons, or is it only for startups?▼

You can use this for open source projects, hackathons, intrapreneurship projects, and learning sessions. The structured questioning applies to any early-stage idea validation or design-phase discussion that requires clear product thinking.

What is the best way to structure a design phase discussion for a new product?▼

The best way to structure a design phase discussion is to use phase-based questioning that confirms the core problem before proposing solutions. This ensures you produce a formal design document capturing real user needs rather than premature implementation details.

Does this office hours approach generate code or just design documents?▼

This office hours approach generates only formal design documents and explicitly forbids code implementation. It clarifies the product problem and desired outcome, delivering a design-focused output to guide downstream technical decisions.