office-hours

Runs YC-style office hours sessions that diagnose product ideas and produce design documents.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill office-hours-bobbo01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-office-hours
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill office-hours-bobbo01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump straight to writing code before validating whether anyone actually wants the product. This Skill forces a structured diagnostic conversation that exposes weak demand evidence, vague target users, and missing wedges before any implementation begins. ## Core Features & Use Cases - Startup Mode Diagnostic: Six forcing questions covering demand reality, status quo competition, desperate specificity, narrowest wedge, user observation, and future-fit, routed by product stage (pre-product, has users, has paying customers). - Builder Mode Brainstorming: Design-thinking sessions for hackathons, side projects, open source, and learning projects. - Design Doc Output: Produces a saved design document instead of code, with a hard gate preventing any implementation action. - Use Case: A founder says "I have an idea for a B2B procurement platform." The skill asks what evidence exists that someone would be upset if it disappeared, pushes past vague answers like "enterprises in healthcare," and ends with one concrete assignment and a design doc. ## Quick Start Ask the assistant to run office hours on your product idea before writing any code.

Frequently Asked Questions about office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a startup idea before building it?

Run an office hours session that asks six forcing questions about demand evidence, the status quo workaround, and the narrowest paid wedge. The session pushes past vague answers until you name a specific person, behavior, or payment, then ends with one concrete assignment.

What questions does a YC office hours session ask?

The six forcing questions cover demand reality, status quo competition, desperate user specificity, the narrowest wedge, direct user observation, and future-fit. Routing depends on stage: pre-product ideas get Q1-Q3, products with users get Q2, Q4, Q5, and products with paying customers get Q4-Q6.

Can I use office hours for hackathon or side projects?

Yes. Builder mode handles hackathons, open source, learning projects, and fun side projects with design-thinking brainstorming instead of the hard startup diagnostic. The mode is chosen based on your stated goal at the start of the session.

Does the office hours skill write code or scaffold projects?

No. A hard gate prohibits invoking implementation skills, writing code, or scaffolding. The only output is a design document saved to the project's gstack directory, intended to feed later planning and review skills.

When should I run office hours in my workflow?

Run it when you describe a new product idea or are deciding whether something is worth building, before any code exists. It is designed to run before plan review skills like /plan-ceo-review or /plan-eng-review.