office-hours

Translate ambiguous startup ideas into actionable design documents through structured questioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/steffenpharai/StartupFramework --skill office-hours-steffenpharai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/steffenpharai/StartupFramework/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/steffenpharai/StartupFramework --skill office-hours-steffenpharai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures startups and builders move from vague ideas to concrete, testable design documents by guiding a problem-first discovery dialogue.

Core Features & Use Cases

  • Guided Phase 1 context gathering to surface goals, constraints, and success metrics.
  • Phase 2 mode selection (Startup mode or Builder mode) to tailor questions and artifacts.
  • Phase 3 Premise Challenge to validate the problem framing and desired outcomes.
  • Phase 4 Alternatives Generation to propose multiple viable approaches and trade-offs.
  • Phase 4.5 Founder Signal Synthesis to capture insights and recommendations for the final design doc.

Quick Start

Describe your startup idea and I will generate a complete YC-style design doc outlining the problem, strategy, 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 vague startup ideas into actionable design docs?

To turn vague startup ideas into actionable design docs, you describe your raw concept to trigger a phase-based discovery dialogue. The system applies context gathering, premise challenging, and alternatives generation to produce a structured YC-style document.

What is the best way to validate a startup problem framing before writing a design document?

Validating startup problem framing requires a structured premise challenge during the design doc creation process. The system evaluates your desired outcomes and tests the core assumptions before finalizing the strategy and next steps.

Can I generate a YC-style design document for builder mode projects?

Yes, you can generate a YC-style design document for builder mode projects by selecting the appropriate exploration mode. The system tailors its phase-based questioning and artifact generation specifically for either startup or builder contexts.

How does phase-based questioning work for creating startup design documents?

Phase-based questioning for startup design documents works by guiding you through context gathering, mode selection, premise challenges, and alternatives generation. This structured dialogue ensures your final document captures essential goals, trade-offs, and founder signals.

Do I need to provide a complete product strategy to start generating a design doc?

No, you do not need to provide a complete product strategy to start generating a design doc. The process is designed to translate ambiguous ideas into clear strategies by surfacing constraints and success metrics through guided questions.

What limitations exist when translating ambiguous ideas into design docs?

A key limitation when translating ambiguous ideas into design docs is the reliance on interactive user responses. The system cannot synthesize accurate founder signals or generate viable alternatives without active participation through the AskUserQuestion protocol.