gstack-openclaw-office-hours

Guides users through phase-driven design doc creation with one-question-at-a-time prompts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured product-design guidance during office-hours sessions, ensuring the problem is understood before proposing solutions and culminating in a formal design document.

Core Features & Use Cases

  • Phase-driven sessions that guide context gathering, premise challenge, and design drafting.
  • One-question-at-a-time prompts (Q1–Q6) to push for specific, evidence-based answers.
  • Generates a structured design doc and stores it in memory for reuse in future sessions.
  • Suitable for founders, builders, and researchers who want actionable design outputs without writing code.

Quick Start

Describe your project goal to begin, then answer the first question in Phase 1 to start building the design doc.

Frequently Asked Questions about gstack-openclaw-office-hours

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

FAQPage Schema
How do I write a design doc for my startup without coding?

To write a design doc without coding, use structured office-hours sessions that guide you through context gathering, premise challenges, and solution sketching. This approach helps builders and founders produce formal design documents through phase-driven prompts.

What is the YC office hours format for product design?

The YC office hours format for product design is a one-question-at-a-time session structure. It enforces specific, evidence-based answers across phases to challenge your premises before drafting a structured design doc.

How do I challenge my startup premises before building a solution?

Challenge startup premises by engaging in phase-driven office-hours sessions that push for evidence-based answers. This process ensures the problem is thoroughly understood before any solution is proposed or sketched.

Can I save and reuse a generated design doc in future sessions?

Yes, you can save and reuse a generated design doc. The session culminates in a formal design document that is automatically stored in memory for reuse in future product-management or builder workflows.

Does this office-hours tool work for researchers as well as founders?

Yes, this office-hours tool works for researchers. It is designed for startup founders, builders, and researchers who need actionable design outputs and structured product-design guidance without writing code.

What are the limitations of one-question-at-a-time design sessions?

A limitation of one-question-at-a-time design sessions is the strict phase-driven format, which requires completing context gathering and premise challenges sequentially before moving to solution sketching and design drafting.