office-hours

Guide product idea evaluation through structured Office Hours sessions.

Updated Apr 18, 2026

Search Tags:#planning #brainstorming #ideation #review #product-management #design-thinking #office-hours

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC Office Hours provides a structured, two-mode framework to rapidly validate ideas, surface risk, and align teams before any code is written.

Core Features & Use Cases

Startup mode: six forcing questions that surface demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit, culminating in a design doc.
Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source.
Proactive invocation: you can trigger this skill before planning reviews to shape strategy and architecture.

Quick Start

Describe your product idea and ask for a structured brainstorming session using the two Office Hours modes.

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 product idea before writing any code?▼

Structured brainstorming validates product ideas before development by applying forcing questions to surface demand reality and risk. This proactive approach aligns teams and generates planning artifacts, saving time by guiding decisions early.

What is the best way to run design thinking brainstorming for side projects?▼

Design thinking brainstorming for side projects runs through a builder mode framework, facilitating ideation for hackathons, learning, and open-source projects. It orchestrates prompts to explore features and guide planning decisions proactively.

How do I use forcing questions to evaluate startup demand?▼

Startup mode uses six forcing questions to evaluate demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. This structured evaluation culminates in a design doc to align strategy before architecture planning.

Can I apply structured ideation sessions for open-source feature exploration?▼

Yes, structured ideation sessions apply to open-source projects through builder mode. This design thinking brainstorming approach guides feature exploration and planning decisions, helping teams evaluate ideas proactively before committing to development.

When should I use startup mode versus builder mode for product management reviews?▼

Use startup mode to validate new product ideas through forcing questions, and builder mode for design thinking brainstorming on side projects or feature exploration. Both modes shape strategy proactively before planning reviews and code development.