gstack-openclaw-office-hours

Enforces product validation through guided questionnaires and generates a design document before coding.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill gstack-openclaw-office-hours-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-office-hours
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-office-hours
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill gstack-openclaw-office-hours-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders and builders frequently waste time and resources building products that lack real market demand, or skip critical problem validation before writing any code. This skill eliminates that risk by enforcing rigorous, YC-style product interrogation to ensure you are solving a real problem for real users before any implementation begins.

Core Features & Use Cases

  • Dual-mode operation: Startup diagnostic mode for founders and intrapreneurs, with six forcing questions to validate demand, status quo, target user, minimum viable wedge, user observation, and future product fit.
  • Builder brainstorm mode: Enthusiastic, collaborative guidance for side projects, hackathons, learning projects, and open source work to help you find the most exciting, deliverable version of your idea.
  • Use cases: Use when you have a new product idea, are asked "is this worth building", want to prepare for YC office hours, or need to think through design decisions before writing any code.

Quick Start

Use the gstack-openclaw-office-hours skill to walk through your new idea for a tool that helps remote teams schedule meetings across time zones and get a validated design document before building 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 a product idea before writing any code?

Validate demand for a product idea by answering six forcing questions covering target users, status quo, minimum viable wedge, user observation, and future product fit, which yields a structured design document before any engineering effort.

What is the best way to prepare for YC office hours with a new startup idea?

Preparing for YC office hours involves running a startup diagnostic using six forcing questions to rigorously validate demand and define a minimum viable product wedge, resulting in a comprehensive design document to guide your pitch.

How do I find a minimum viable wedge for my side project?

Find a minimum viable wedge for a side project by using builder brainstorm mode, which provides enthusiastic, collaborative guidance to help you identify the most exciting and deliverable version of your idea before implementation.

Can I use this product validation framework for hackathon projects?

Yes, you can use this product validation framework for hackathon projects through its builder brainstorm mode, which helps participants find the most exciting, deliverable version of an idea without writing implementation code.

Does this product validation skill generate source code or just design documents?

This product validation skill generates only mandatory design documents and performs no implementation code generation, strictly enforcing rigorous product validation to prevent wasted engineering effort on unproven ideas.