gstack-openclaw-office-hours

Run YC-style office hours diagnostics to validate product ideas and generate design documents.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill gstack-openclaw-office-hours-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill gstack-openclaw-office-hours-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of wasting time and resources on unproven product ideas by providing structured, YC office hours-style guidance to validate problem-solution fit and design direction before any implementation work begins.

Core Features & Use Cases

  • Dual-mode adaptive workflow: Switches between rigorous YC-style diagnostic questioning for startup founders and intrapreneurs, and enthusiastic collaborative brainstorming for hackathon participants, side project builders, and learners.
  • Demand and fit validation: Forces specificity around real user demand, pain points, and narrowest viable product wedges to avoid common founder failure patterns like solution-in-search-of-a-problem.
  • Formal design doc generation: Produces actionable design documents with alternatives analysis, premise validation, and concrete next steps instead of implementation code.
  • Use Case: A startup founder with a new B2B SaaS idea can use this skill to run through targeted diagnostic questions to confirm real customer demand before writing any code, while a hackathon participant can use it to refine their demo idea into a compelling, shippable project in hours.

Quick Start

Use the gstack-openclaw-office-hours skill to run a YC-style office hours session for your new product idea to validate demand and generate a design document before writing any code.

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 my startup idea before writing any code?

To validate a startup idea before coding, you can run structured YC office hours-style diagnostic questioning to test problem-solution fit, confirm real user demand, and identify the narrowest viable product wedge.

What is the best way to draft a product design document for pre-build planning?

The best way to draft a pre-build product design document is through structured brainstorming that produces formal design specs with alternatives analysis, premise validation, and concrete next steps instead of implementation code.

Can I use YC office hours style brainstorming for hackathon projects and side projects?

Yes, YC office hours style brainstorming adapts for hackathon projects and side projects by switching from rigorous diagnostic questioning to enthusiastic collaborative ideation to refine demo ideas into shippable projects.

How do I test demand and problem-solution fit for a B2B SaaS idea?

To test demand and problem-solution fit for a B2B SaaS idea, structured diagnostic workflows force specificity around real user pain points and narrowest viable product wedges to avoid building a solution in search of a problem.

Does this product ideation process generate implementation code for my startup?

No, this product ideation process does not generate implementation code; it operates under strict guardrails to produce only formal design documents with alternatives analysis, premise validation, and actionable next steps.

When do I need to run idea evaluation workflows for intrapreneurship?

You need to run idea evaluation workflows for intrapreneurship when evaluating new product viability, ensuring real user demand exists, and establishing formal design directions before committing development resources.