office-hours

Pressure-test product ideas with YC office-hours style forcing questions and design-doc output.

6|2|Updated Oct 18, 2021
One-click install
npx skills add https://github.com/jerrywu001/jerrywu001 --skill office-hours-jerrywu001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/office-hours
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill office-hours-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you pressure-test a product idea before any implementation by forcing crisp, evidence-based clarity about who wants it, what they do today, and what the smallest paid wedge could be.

Core Features & Use Cases

  • Six forcing questions for startup diagnostics (Startup mode): Demand reality, status quo, desperate specificity, narrow wedge, observation & surprise, and future-fit, producing concrete next assignments.
  • Builder-mode design partner brainstorming: Generates delightful, shippable design directions for side projects, hackathons, open source, learning, and research.
  • Design-doc output (no code): Produces a structured design document aligned to the mode and your stated goal.

Quick Start

Ask for an office-hours partner by saying: "Run office hours on my idea: [describe the product in 3-5 sentences], and tell me what you need from me first."

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I pressure-test a product idea before implementation?▼

To pressure-test a product idea before implementation, you can run a YC-style office hours diagnostic that applies structured forcing questions to validate demand reality and identify your smallest paid wedge. It captures results into a structured design document.

What is demand validation for startup diagnostics?▼

Demand validation for startup diagnostics is the process of evaluating demand reality, status quo, and desperate specificity through six forcing questions. It produces concrete next assignments to determine if a product is worth building.

How do I brainstorm design directions for a side project or hackathon?▼

To brainstorm design directions for a side project or hackathon, use builder-mode design partner brainstorming. It generates delightful, shippable design directions for open source, learning, and research projects without writing code.

Can I generate a design document without writing any code?▼

Yes, you can generate a design document without writing code. The tool operates under allowed tool constraints with no implementation actions, producing a structured design doc aligned to your stated goal and mode.

Does this work for both startup founders and side project builders?▼

Yes, it works for both startup founders and side project builders by routing them into appropriate workflows. Startup mode applies diagnostics for demand validation, while builder mode focuses on design partner brainstorming.