skills.rest
curielmc
curielmcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

office-hours

Generate YC-style design docs with problem statements and next-step plans.

Updated Feb 27, 2026
Search Tags:#planning#startup#AskUserQuestion#design-doc#problem-framing#phase-1#office-hours
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill office-hours-curielmc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/curielmc/beat-SPY --skill office-hours-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps YC office-hours partners clarify problems and craft rigorous design docs by guiding context gathering and structured questioning.

Core Features & Use Cases

  • Generate a structured YC-style design doc from a startup idea, including a clear problem statement, assumptions, and next-step plan.
  • Use the six forcing questions to push for specific evidence and risky edge cases, ensuring a complete plan.
  • Align discussions around phase-appropriate activities (context gathering, problem framing, planning) and produce actionable output.

Quick Start

Describe your project goal and current plan, and I will generate a concise YC-style design doc with hard questions and a next-step plan.

Frequently Asked Questions about office-hours

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a startup idea into a structured design doc?▼

A YC-style design doc includes a clear problem statement, identified assumptions, and a structured next-step plan, generated by applying six forcing questions to push for specific evidence and risky edge cases.

How do I frame startup problems using structured questioning?▼

To frame startup problems using structured questioning, the skill applies six forcing questions during context gathering to push for specific evidence and uncover risky edge cases, ensuring your problem statement is rigorous and complete.

Can I use this for phase 1 startup planning and context gathering?▼

Yes, this skill is designed specifically for phase 1 startup planning, aligning discussions around context gathering, problem framing, and actionable next-step planning to drive early builder decisions.

What's the best way to validate assumptions in a startup design doc?▼

The best way to validate assumptions in a startup design doc is applying the six forcing questions to push for specific evidence and test risky edge cases, ensuring your plan is complete before moving forward.

Do I need a fully developed plan to start writing a design doc?▼

No, you do not need a fully developed plan to start writing a design doc, you only need to describe your project goal and current plan to initiate the structured questioning and context gathering process.

Related Skills

Explore More Education & Research Skills→
OzeroHAXOzeroHAX
32

docs-project-brief

Define project context, problem statement, and MVP boundaries.

Community
Basic
chenwei791129chenwei791129
1

spectra-discuss

Facilitate structured technical discussions to reach architectural decisions.

Community
Intermediate
anishs1207anishs1207
1

office-hours

Turn vague startup ideas into structured design docs with risks and next steps.

Community
Advanced
jeisenbackjeisenback

office-hours

Draft YC-style design docs from startup ideas or product concepts.

Community
Advanced