gstack-openclaw-office-hours

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

Guide a YC-style office-hours session to produce a structured design document.

Updated May 6, 2026

Search Tags:#startup #design-doc #design-thinking #phase-driven #office-hours #build-not-code

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides a YC-style office-hours session to produce a structured design-doc workflow that surfaces a clear problem, exploration phases, and a concrete next action, without writing any code.

Core Features & Use Cases

Phase-driven design process: follows a six-phase YC-style office-hours framework to gather context, diagnose premises, compare approaches, and synthesize a final design doc.
Design-first collaboration: outputs a formal design document to guide future implementation, not code.
Structured prompts and guidance: provides phased prompts, premise challenges, alternative paths, and a synthesis flow to help teams align on next steps.
Use cases: founders seeking quick, rigorous feedback on ideas; educators teaching design thinking; product teams prototyping.

Quick Start

Walk me through Phase 1 and prepare a draft design doc following the six-phase YC office-hours process.

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 validate a startup idea without writing code?▼

To validate a startup idea without writing code, use a YC-style office-hours design process. This framework guides you through six phases to diagnose premises, compare alternatives, and output a structured design document for decision-making.

What is a phase-driven design doc workflow for founders?▼

A phase-driven design doc workflow is a structured, six-phase YC office-hours process. It captures project context, challenges premises, evaluates alternative paths, and synthesizes everything into a formal design document instead of generating code.

Can I use design-thinking office hours for rapid idea brainstorming?▼

Yes, design-thinking office hours support rapid idea brainstorming and validation. By providing project context and goals, you receive phase-wise prompts that surface open questions and produce a draft design document for your team.

How do I start a YC-style office-hours session for design-first thinking?▼

To start a YC-style office-hours session, provide your project context and goals. The process begins with Phase 1 context gathering and sequentially guides you through premise diagnosis, approach comparison, and final design doc synthesis.

Does this design-first approach require any coding prerequisites?▼

No coding prerequisites are required. This approach is strictly build-not-code, focusing entirely on design-first thinking to produce a structured design document that guides future implementation rather than generating functional code.