office-hours

Diagnose product ideas through YC-style forcing questions and produce design documents.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill office-hours-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill office-hours-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump straight into building before validating whether anyone actually wants the product. This Skill runs a structured YC office hours session that stress-tests demand, target users, and scope before any code is written, and saves the outcome as a design document. ## Core Features & Use Cases - Startup Mode Diagnostic: Six forcing questions covering demand reality, status quo workarounds, desperate specificity, narrowest wedge, user observation, and future-fit, routed by product stage (pre-product, has users, has paying customers). - Builder Mode Brainstorming: Design-thinking collaboration for hackathons, side projects, learning, and open source ideas. - Design Doc Output: Produces a saved design document instead of code, with a hard gate preventing any implementation action. - Use Case: A founder says "I have an idea for an AI tool for developers." The Skill asks one forcing question at a time, pushes past vague answers like "enterprises in healthcare," and ends with a concrete next action and a written design doc. ## Quick Start Ask the assistant to run office hours on your new product idea before writing any code.

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 building it?

Run a structured diagnostic that asks forcing questions about demand evidence, current workarounds, and your narrowest payable wedge. This Skill asks them one at a time, pushes past vague answers, and saves the conclusions as a design document.

What questions does YC ask in office hours?

The six core questions cover demand reality, status quo workarounds, desperate specificity of the target user, the narrowest payable wedge, observed user behavior surprises, and future-fit. Which questions apply depends on whether you are pre-product, have users, or have paying customers.

Can I use office hours for hackathon or side projects?

Yes. Builder mode handles hackathons, open source, learning, and fun projects with design-thinking brainstorming instead of the hard startup diagnostic. The goal question at the start routes you to the right mode.

Does the office hours skill write code or scaffold projects?

No. It has a hard gate prohibiting any implementation skill, code writing, or scaffolding. Its only output is a design document, and it is meant to run before planning or engineering review skills.

When should I run office hours in my workflow?

Run it when you have a new idea or are deciding whether something is worth building, before any code exists. It is designed to precede plan-ceo-review and plan-eng-review so the problem is validated first.