office-hours

Guides product idea brainstorming through six YC-style diagnostic questions and writes a design doc.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill office-hours-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/NalinDalal/skillset/tree/main/skills/workflow/office-hours
Command: npx skills add https://github.com/NalinDalal/skillset --skill office-hours-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump straight into code before validating whether an idea is worth building. This Skill forces structured thinking about demand, competition, and scope before any implementation begins, producing a written design doc instead of premature code. ## Core Features & Use Cases - YC Product Diagnostic: Six forcing questions covering demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit, asked one at a time with pushback on weak framing. - Dual Modes: Startup and intrapreneurship ideas get the full YC diagnostic; hackathons, side projects, learning, and open source get a lighter builder-mode design partner flow. - Design Doc Output: Writes a structured design document to docs/designs/ covering problem, context, goals, non-goals, approach options, recommendation, and open questions. - Use Case: You have a new product idea and say "help me think through this". The Skill gathers codebase context, asks your goal, walks you through the diagnostic questions, presents 2-3 implementation approaches with tradeoffs, and saves a design doc you can share or build from. ## Quick Start Ask the agent to run office hours on your new product idea and answer each diagnostic question as it comes.

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 code?▼

Run the office hours flow, which asks six diagnostic questions one at a time: who has the problem, what they use today, the exact pain moment, the narrowest wedge, your personal observations, and the 12-month vision. Weak answers get pushback before a design doc is written.

What questions does YC ask about product ideas?▼

The diagnostic covers demand reality, status quo alternatives, desperate specificity of the pain moment, the narrowest wedge for v1, firsthand observation of the problem, and future-fit. Each answer is reflected back and challenged where framing is vague.

Does office hours write any code?▼

No. The Skill explicitly does not write code. Its only output is a design document saved to docs/designs/ containing the problem, context, goals, non-goals, approach options, recommendation, and open questions.

Can I use office hours for hackathon or side projects?▼

Yes. Goal detection routes non-startup ideas to builder mode, which asks about the spark, ideal user, unconstrained vision, MVP scope, and the minimum you would be proud to ship. Startup and intrapreneurship ideas get the full YC diagnostic instead.

When should I not use a design doc brainstorming flow?▼

Skip it when requirements are already settled and you need implementation, bug fixes, or code review. The Skill is designed for the pre-code phase where the problem, audience, and scope are still undecided.