office-hours

Generate a Phase 1–4 design doc with problem statement and next actions.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/XinheLIU/human-leverage --skill office-hours-xinheliu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/office-hours
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill office-hours-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates turning vague startup ideas and questions into a clear, design-doc style artifact that can drive YC Office Hours conversations and decisions. It helps teams align on the problem, define a minimal wedge, and produce concrete next steps, reducing drift and ambiguity during early discussions.

Core Features & Use Cases

  • Phase-driven problem understanding and design directions for startup ideas and side projects.
  • Guided, structured dialogue that surfaces specific evidence, risks, and next actions.
  • Output a repeatable design doc that can be reviewed, iterated, and shared with mentors or teammates.

Quick Start

Tell me your startup idea and current challenge, and I will generate a complete YC office-hours design doc with the problem, plan, and next steps.

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 vague startup idea into a structured design doc for YC office hours?

To turn a vague startup idea into a design doc for YC office hours, provide your concept and current challenge to generate a Phase 1–4 document defining the problem, strategic plan, and concrete next actions.

What is the best way to define a minimal wedge for an early-stage startup project?

Defining a minimal wedge for an early-stage startup involves guided, structured dialogue that surfaces specific evidence and risks, helping teams align on a focused problem statement and actionable next steps.

How do I structure phase planning and action steps for a hackathon or intrapreneur project?

Structuring phase planning and action steps for hackathons or intrapreneur projects requires applying a phase-driven approach to problem understanding, which outputs a repeatable design doc to review and iterate on.

Can I use this design doc approach for side projects or learning sessions, and what inputs do I need?

You can use this design doc approach for side projects and learning sessions by providing your initial idea and current challenge, which the system processes through structured prompts to elicit specific details and output a strategic plan.

Why does my startup problem definition drift during early discussions with mentors?

Startup problem definition drifts during early discussions due to ambiguity, which this approach reduces by facilitating structured dialogue that aligns your team on the problem and defines a minimal wedge before generating concrete next steps.