gstack-openclaw-office-hours

Name: gstack-openclaw-office-hours
Availability: InStock
Author: bizzybae

Guide six-phase office hours to produce a design document template.

Updated Apr 5, 2026

Search Tags:#startup #phases #builder #product-management #design-doc #office-hours

Ready to run

npx skills add https://github.com/bizzybae/qstack --skill gstack-openclaw-office-hours-bizzybae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/bizzybae/qstack/tree/main/gstack-original/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/bizzybae/qstack --skill gstack-openclaw-office-hours-bizzybae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams understand and frame a problem space during focused office hours, ensuring alignment before solutions are proposed.

Core Features & Use Cases

Guided six-phase design session (Phase 1-6) to extract problem details, user roles, and success criteria.
Generates a structured design doc template and a clear Premises, Approaches, and Next Steps.
Works as a design partner for startup, intrapreneurship, or builder projects seeking a disciplined, non-implementation brainstorming process.

Quick Start

Schedule a focused design session and follow the six-phase process to generate a design document.

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 structure a design doc during YC office hours for my startup?▼

Structure a design doc by applying phase-based modes during office hours to collect evidence, user roles, wedges, and constraints. This process guides the creation of a formal design document template with premises, approaches, and next steps, strictly excluding implementation details.

What is the best way to frame a product management problem before proposing solutions?▼

Framing a product management problem requires a guided six-phase design session to extract problem details, user roles, and success criteria. This enforces alignment before solutions are proposed, ensuring teams understand the problem space during focused office hours.

Can I use this design doc process for intrapreneurship or builder projects?▼

Yes, you can use this process for builder or intrapreneurship projects. It applies phase-based modes to collect evidence and constraints, working as a disciplined, non-implementation brainstorming design partner for any product team seeking structured alignment.

How do I identify user roles and wedges for my product design document?▼

Identify user roles and wedges by following the staged questioning process during office hours. This method strictly extracts problem details and constraints, guiding the creation of a formal design document template without including any implementation details.

Does this office hours partner generate implementation details for engineering teams?▼

No, it does not generate implementation details. It enforces strict session rules to deliver a formal design doc template, focusing entirely on premises, approaches, and next steps to ensure alignment before any engineering solutions are proposed.