gstack-openclaw-office-hours

Guide teams through YC office hours phases to produce structured design docs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams convert vague ideas into structured design documentation before any code is written, aligning stakeholders and reducing rework.

Core Features & Use Cases

  • Phase-driven YC office-hours guidance that focuses on problem framing, scope, and solution design rather than implementation.
  • A step-by-step workflow (context gathering, diagnostics, premise challenge, alternatives, and final design doc) that surfaces concrete next steps.
  • Generates a formal design artifact and an actionable assignment to validate ideas quickly.

Quick Start

Share your project goal and any existing context, and I will generate a design doc through the Office Hours workflow.

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 convert a vague startup idea into a structured design doc before coding?

To convert a vague idea into a structured design doc, use a YC office hours partner workflow that guides your team through context gathering, premise challenges, and alternative evaluations to produce a formal design artifact.

What is the best way to validate project scope and problem framing for a hackathon?

Validating project scope for a hackathon involves running phase-driven diagnostics that challenge your core premises and surface concrete next steps, ensuring stakeholders align on the problem before any implementation begins.

Can I use this YC office hours workflow for internal project design validation?

Yes, you can use this office hours workflow for internal project design validation, as it is specifically applicable to startups, internal projects, hackathons, or research sessions where early design validation is essential.

How does the design doc generation process work during an office hours session?

The design doc generation process works through strict session phases: context gathering, diagnostics, premise challenge, exploring alternatives, and finalizing a formal design artifact with an actionable assignment to validate ideas quickly.

Do I need existing project context to start generating a design document?

You do not need extensive existing project context to start; simply sharing your project goal and any available context is sufficient to initiate the office hours workflow and generate a design doc.