skills.rest
TumeloRamaphosa
TumeloRamaphosaCOMMUNITY
Explore all skills by this author →
GitHub

office-hours

Evaluate product ideas into actionable YC-style design docs.

Updated May 7, 2026
Search Tags:#idea validation#design doc#startup strategy#product brainstorming#side project planning#YC forcing questions
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill office-hours-tumeloramaphosa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill office-hours-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The office-hours skill helps you avoid building the wrong thing by forcing clarity on demand, specificity, and your most promising wedge. It also reduces “blank page” thinking by turning rough product or side-project ideas into a structured design doc you can act on.

Core Features & Use Cases

  • YC-style idea validation (startup mode): Uses six forcing questions to expose real demand reality, your status quo, what makes the problem painful, the narrowest wedge to start with, key observations, and how future-fit it is.
  • Builder brainstorming (builder mode): Generates design-thinking brainstorming for side projects, hackathons, learning goals, and open source contributions, shaped into a usable document.
  • Design doc output: Saves a design doc so you can move directly into plan reviews like plan-ceo-review or plan-eng-review instead of starting over.

Quick Start

Use the skill when you have a new product idea and want it stress-tested and structured into a design doc: “office-hours this idea so we can decide the narrowest wedge and write the 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 a product idea before writing any code?▼

Product idea validation uses YC-style forcing questions to test real demand, assess the status quo, and identify your narrowest wedge. This exposes whether the problem is painful enough to build. It outputs a structured design doc for immediate planning.

What is the best way to turn a rough side project idea into a design doc?▼

Turning a rough side project idea into a design doc uses design-thinking brainstorming to shape hackathon or open source goals into a usable document. It applies builder mode to structure exploration. The output routes directly into plan reviews without starting over.

How do I run a YC-style idea validation check on my startup strategy?▼

Running a YC-style idea validation check applies six forcing questions to your startup strategy to evaluate real demand, problem severity, and future-fit. This stress-tests your wedge and key observations. It generates a structured design doc to guide implementation.

Does idea validation work for early side project planning and hackathons?▼

Idea validation works for early side project planning and hackathons by using builder mode to generate design-thinking brainstorming. It shapes learning goals and open source contributions into a usable document. This prevents building the wrong thing before code exists.

What should I do after generating a design doc for a new product idea?▼

After generating a design doc for a new product idea, you should move directly into plan reviews like plan-ceo-review or plan-eng-review. The design doc output is structured for this exact routing. This prevents starting over during pre-implementation exploration.

Why do I need forcing questions for pre-implementation exploration?▼

Forcing questions are needed for pre-implementation exploration to demand clarity on specificity and your most promising wedge. They reduce blank page thinking by exposing real demand reality. This ensures you avoid building the wrong thing before writing code.

Related Skills

Explore More Product & Management Skills→
robertzengcnrobertzengcn

office-hours

Validate product and startup ideas through structured forcing questions.

Community
Advanced
Intension-usIntension-us

office-hours

Plan two-mode office-hours sessions to validate product ideas and generate design docs.

Official
Advanced
ShmurdocShmurdoc

office-hours

Guide startup founders through six forcing questions to validate product demand.

Community
Advanced
cegit27cegit27
3

office-hours

Validate product ideas with YC-style forcing questions before writing code.

Official
Advanced