office-hours

Guide product ideation through six structured questions and generate a Markdown design document.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill office-hours-akiyoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/office-hours
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill office-hours-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC office hours partner helps teams clarify product ideas by prompting six structured questions, ensuring the problem is understood before solution design and producing a design document for downstream skills.

Core Features & Use Cases

  • Structured questioning: guides teams through the six forcing questions to surface core needs.
  • Design document generation: outputs a ready-to-hand-off design document.
  • Reusable session framework: applies to new features, pivots, or early-stage ideation sessions.

Quick Start

Describe your product idea and start the six-question office-hours process to generate a design document.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I clarify a startup product idea before building anything?

Product ideation through structured questioning helps teams surface core needs before solution design. It applies six YC-style forcing questions to early-stage ideas, producing a design document for downstream implementation without writing any code.

What is the best way to structure feature brainstorming for an early-stage product?

The best way to structure feature brainstorming is through a reusable YC-style office-hours framework. It guides teams with six questions to challenge premises and outputs a design document ensuring the core problem is fully understood first.

How do I generate a design document for downstream development from a rough idea?

Generate a design doc from a rough idea by running YC-style office hours. Describe the concept, answer six structured questions to collect context, and output a handoff-ready Markdown design document for downstream development.

Can I use this questioning framework for a startup pivot or only new product ideation?

You can use this questioning framework for both new product ideation and startup pivots. The reusable session framework applies the same six guiding questions to challenge premises and clarify core needs across different early-stage scenarios.

What are the limitations of using YC-style office hours for product design?

A key limitation is that this office-hours process takes no implementation actions; it strictly produces a design document. It focuses entirely on early-stage ideation and questioning premises, leaving actual development to downstream skills.