office-hours

Orchestrate structured design sessions converting startup ideas into formal design documents.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/EhsaanArk/ai-signal-router --skill office-hours-ehsaanark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/EhsaanArk/ai-signal-router/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/EhsaanArk/ai-signal-router --skill office-hours-ehsaanark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC founders often struggle to translate raw ideas into clear, testable design decisions. This skill acts as a design-partner that guides rigorous questioning and documents a complete design plan without writing code.

Core Features & Use Cases

  • Phase-based discovery: Context gathering, design partnership, and planning phases to surface critical assumptions and next steps.
  • One-question-at-a-time interrogation: Uses AskUserQuestion prompts to drive precise, evidence-based answers.
  • Output-first philosophy: Produces a plan-ready design document capturing problem framing, scope, success criteria, and action items for the team.

Quick Start

Describe your idea and goals, and I will generate a complete YC-style design document outline.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I convert a startup idea into a formal design document?

Structured design sessions convert raw startup ideas into formal design documents by applying a phased workflow that surfaces critical assumptions and produces plan-ready design artifacts without writing code.

What is the best way to frame a startup problem before building a product?

Rigorous problem framing for startups is achieved through one-question-at-a-time discovery, which interrogates your idea sequentially to extract evidence-based answers, define scope, and establish clear success criteria.

Can I use phase-based discovery to plan next steps for an early-stage startup?

Yes, phase-based discovery guides early-stage builders through context gathering, design partnership, and planning phases to surface critical assumptions and document actionable next steps for the team.

Does this approach generate code or just design plans for my startup?

This approach follows an output-first philosophy that produces design documents capturing problem framing, scope, success criteria, and action items, rather than generating any application code.

How do YC office hours work for validating a startup idea?

YC-style office hours act as a design partner that drives precise questioning to translate your raw goals into clear, testable design decisions and a complete design plan.

What limitations exist when using one-question-at-a-time interrogation for design planning?

The one-question-at-a-time interrogation requires sequential, focused responses to generate a design document, making it less suited for teams needing rapid, unstructured brainstorming instead of rigorous, evidence-based discovery.