office-hours

Generate design documents from startup ideas using YC Office Hours-style questioning.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill office-hours-kakarottoooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/office-hours
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill office-hours-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous startup ideas into concrete, review-ready design documents using structured YC Office Hours-style questioning.

Core Features & Use Cases

  • Structured Q&A workflow that surfaces critical assumptions and validation criteria.
  • Generates a complete design doc capturing problem framing, wedge, future-fit scenarios, and decisions.
  • Works for startups, internal projects, hackathon ideas, and ideation sessions.

Quick Start

Describe your project idea and desired outcome to generate a design doc.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I generate a design doc from a startup idea?

To generate a design doc from a startup idea, describe your project concept and desired outcome. The system applies YC Office Hours-style questioning to frame problems, validate demand, and capture decisions into a structured document.

What is the best way to validate demand for an early-stage project concept?

Validating demand for an early-stage project involves structured questioning that surfaces critical assumptions. This approach uses YC Office Hours-style problem framing to identify validation criteria and define a market wedge before building.

Can I use YC Office Hours-style questioning for internal initiatives and hackathon concepts?

Yes, you can use YC Office Hours-style questioning for internal initiatives and hackathon concepts. The workflow applies to pre-product and early-stage projects to frame problems and capture decisions without writing code.

How does problem framing work for pre-product startup concepts?

Problem framing for pre-product concepts works by applying structured Q&A to surface assumptions and define a market wedge. This process converts ambiguous ideas into a review-ready design document with a log of guiding questions.

Do I need to write code to define a wedge for my startup idea?

No, you do not need to write code to define a wedge. The workflow enforces a no-code design-doc process, capturing problem framing and future-fit scenarios through structured questioning rather than implementation.

What is included in the output when converting an ambiguous idea into a design doc?

Converting an ambiguous idea into a design doc outputs a structured document capturing problem framing and wedge, a log of guiding questions from the session, and a record of validated decisions for early-stage projects.