office-hours

Facilitate structured brainstorming sessions and capture decisions in a design doc.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC Office Hours provides a structured, dual-mode approach to brainstorming that helps teams surface reality-based product ideas, surface critical assumptions, and capture decisions in a concrete design doc.

Core Features & Use Cases

  • Two modes: Startup mode guides users through six forcing questions to expose demand reality, status quo, desperate specificity, narrow wedge, observation, and future-fit. Builder mode enables design thinking brainstorming for side projects, hackathons, learning, and open source, always saving a design doc.
  • Proactively invoked when asked to brainstorm, evaluate whether something is worth building, or plan a product concept, ensuring that sessions produce actionable outputs rather than vague ideas.
  • Outputs include a prioritized plan and a formal design document ready for review.

Quick Start

Initiate an office-hours session to brainstorm a product idea and capture a design doc.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I validate product ideas and capture decisions in a design doc?

Structured brainstorming for product management validates ideas by surfacing critical assumptions and stakeholder input, directly capturing decisions in a formal design doc. This ensures early ideation produces actionable plans rather than vague concepts.

What is the best way to structure a brainstorming session for a hackathon or side project?

The best way to structure brainstorming for side projects or hackathons is using a builder mode that applies design thinking principles. It guides you through ideation and automatically saves the outputs as a documented design plan suitable for immediate review and execution.

How do I run a strategy review to surface critical product assumptions?

Running a strategy review to surface critical product assumptions requires a structured questioning process. By applying six forcing questions covering demand reality, status quo, and narrow wedge, you expose hidden assumptions and document them in a prioritized plan.

Does this brainstorming approach work for evaluating whether a product is worth building?

Yes, this brainstorming approach is proactively invoked to evaluate whether something is worth building. It forces you to examine desperate specificity, observation, and future-fit, ensuring you assess real demand before committing development resources to a concept.

What do I need to draft a design doc suitable for stakeholder review?

To draft a design doc suitable for stakeholder review, you need a structured planning session that uses plan-mode prompts and an AskUserQuestion flow. This captures stakeholder input and surfaces reality-based decisions, outputting a formal documented design plan.