office-hours

Generates a formal design document with decisions, tradeoffs, and next steps from user-provided context.

5|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/forbotsake/forbotsake --skill office-hours-forbotsake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/forbotsake/forbotsake/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/forbotsake/forbotsake --skill office-hours-forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns teams on core product questions and yields a shareable design doc that guides planning, reviews, and execution.

Core Features & Use Cases

  • Two modes: Startup mode with six forcing questions to surface demand reality and a Builder mode for design-thinking brainstorming on side projects, learning, and open source initiatives.
  • Proactively invoke and route discussions to design reviews and planning checkpoints, producing a persistent design doc that captures decisions, tradeoffs, and next steps.
  • Outputs are designed to be loaded into project context during activation and referenced later for alignment and governance.

Quick Start

Describe your product idea and start a YC office hours 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 write a design doc for a product idea?▼

To write a design doc for a product idea, you must provide initial context and undergo structured, design-first exploration. This process prompts targeted questions to surface assumptions and outputs a formal document with decisions, tradeoffs, and next steps.

What is structured brainstorming for startup validation?▼

Structured brainstorming for startup validation is a design-first exploration process that uses forcing questions to surface demand reality. It aligns teams on core product questions and yields a shareable design doc for planning and execution.

Can I use design docs for open source side projects?▼

Yes, you can use design docs for open source side projects by engaging Builder mode. This mode facilitates design-thinking brainstorming to validate ideas, align planning, and produce persistent documentation for learning and open source initiatives.

What's the best way to align teams on product decisions and tradeoffs?▼

The best way to align teams on product decisions and tradeoffs is generating a formal design doc through guided exploration. This persistent document captures decisions, tradeoffs, and next steps for ongoing alignment, governance, and plan reviews.

Do I need to provide context before starting a design review?▼

Yes, you must provide user-provided context before starting a design review. The guided exploration requires this initial input to prompt targeted questions, surface assumptions, and produce a structured design document with actionable next steps.