office-hours

Runs YC-style office hours sessions that produce design documents for product ideas.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill office-hours-lgj-jonathan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack/office-hours
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill office-hours-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump straight to code before validating whether anyone actually wants the thing. This Skill forces a structured diagnostic conversation — demand evidence, status quo, narrowest wedge — before any implementation, and captures the result as a design document. ## Core Features & Use Cases - Startup Mode: Six YC-style forcing questions (demand reality, status quo, desperate specificity, narrowest wedge, observation, future-fit) asked one at a time with pushback until answers are specific and evidence-based. - Builder Mode: Design-thinking brainstorming for hackathons, side projects, learning, and open source work. - Design Doc Output: Saves a design document per project; explicitly refuses to write code or invoke implementation skills. - Use Case: You have a new product idea and want to know if it is worth building. Run office hours before any planning or coding to stress-test demand and scope the smallest viable wedge. ## 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 office hours to answer six forcing questions about demand evidence, the status quo workaround, and the narrowest paid wedge. The session pushes until answers are specific and produces a design doc, not code.

What is the difference between startup mode and builder mode?▼

Startup mode applies the rigorous YC diagnostic for founders and intrapreneurs pursuing commercial outcomes. Builder mode uses design-thinking brainstorming for hackathons, learning, open source, and fun side projects.

Can office hours write code or scaffold my project?▼

No. The skill has a hard gate prohibiting code, scaffolding, or implementation skills. Its only output is a design document; implementation happens later through separate planning and 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 in the gstack workflow.

What are the limitations of an AI office hours session?▼

The diagnostic depends entirely on the honesty and specificity of your answers; it cannot verify market claims or talk to your customers. It produces a design doc and one concrete next action, not customer interviews or revenue.