office-hours

Produces design documents through YC-style forcing questions and design thinking brainstorms.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill office-hours-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/office-hours
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill office-hours-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Founders and builders often jump straight into code before validating whether an idea is worth building. This Skill runs a structured office-hours session that interrogates demand, users, and scope before any implementation, producing a design document instead of code. ## Core Features & Use Cases - Startup Mode (YC Diagnostic): Six forcing questions on demand evidence, status quo, target user, narrowest wedge, user observation, and future-fit, asked one at a time with pushback on vague answers. - Builder Mode (Design Partner): Generative brainstorm questions for hackathons, side projects, open source, and learning projects, focused on the most exciting version of the idea. - Premise Challenge & Landscape Awareness: Challenges problem framing, searches existing design docs for overlap, and optionally researches conventional wisdom via web search before proposing solutions. - Use Case: A founder says "I have an idea for an AI tool for developers." The skill asks who specifically needs it, what they do today, and what the smallest paid version looks like, then writes a design doc capturing the validated direction. ## Quick Start Ask the assistant to run office hours on your new product idea and answer the forcing questions to get 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 building it?

Run an office-hours session that asks six forcing questions covering demand evidence, current workarounds, the specific target user, the narrowest paid wedge, observed user behavior, and future relevance. The output is a design document, not code.

What is the difference between Startup mode and Builder mode?

Startup mode applies YC-style diagnostic questions with direct pushback for founders and intrapreneurs. Builder mode is an enthusiastic brainstorm for hackathons, open source, learning, and fun projects, ending in concrete build steps rather than validation tasks.

Does the office-hours skill write any code?

No. The skill has a hard gate prohibiting code, scaffolding, or implementation actions. Its only output is a design document capturing the validated problem, user, and scope decisions.

Can I skip the forcing questions if I already have a plan?

Yes. If you express impatience or provide a fully formed plan with real evidence such as users or revenue, the skill fast-tracks to the premise challenge and alternatives phases. A full skip requires concrete demand evidence.

Does the skill search the web during ideation?

Only with your permission. The landscape awareness phase asks before searching, uses generalized category terms rather than your specific idea, and can be skipped entirely to keep the session private.