office-hours

Validate product ideas with structured YC-style office hours diagnostics.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill office-hours-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/office-hours
Command: npx skills add https://github.com/ajsai47/holyclaude --skill office-hours-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of jumping into implementation before validating whether a product idea is worth building. Founders and builders often waste weeks coding something nobody wants. This skill forces the hard questions about demand, specificity, and user pain before any code is written.

Core Features & Use Cases

  • Startup Mode: Six forcing questions that expose demand reality, status quo, narrowest wedge, and future-fit for startup founders.
  • Builder Mode: Design thinking brainstorming for side projects, hackathons, learning, and open source contributions.
  • Design Doc Output: Produces a structured design document that captures the thinking and can be handed to engineering.
  • Use Case: A founder with a new SaaS idea uses this to validate whether the problem is real before hiring engineers or writing code.

Quick Start

Use the office-hours skill to think through your new product idea and generate a design document.

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

You can validate a product idea by applying YC-style office hours diagnostics that force hard questions about demand reality and user pain. This structured brainstorming process produces a design document capturing status quo analysis and narrowest wedge, ensuring you validate demand before writing code or hiring engineers.

What is the best way to brainstorm and validate side projects or hackathon ideas?

The best way to validate side projects is using Builder Mode design thinking diagnostics. This structured brainstorming approach assesses the narrowest wedge and future-fit of your idea, producing a design document that captures your thinking before you start building.

How does a YC office hours diagnostic evaluate product demand?

A YC office hours diagnostic evaluates product demand by asking six forcing questions that expose demand reality and analyze the status quo. It checks whether the problem is specific enough and assesses future-fit, ensuring founders validate real user pain before committing to implementation.

Can I use this to generate a design document for engineering handoff?

Yes, you can use this validation process to generate a structured design document for engineering handoff. The output captures demand reality, status quo analysis, and the narrowest wedge, allowing you to hand clear product specifications directly to your engineering team.

What is the difference between Startup Mode and Builder Mode for idea validation?

Startup Mode focuses on six forcing questions to expose demand reality and future-fit for startup founders. Builder Mode applies design thinking brainstorming for side projects, hackathons, learning, and open source contributions, tailoring the idea validation process to the builder's context.