office-hours

Convert ambiguous startup ideas into structured design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders often struggle to articulate vague ideas into concrete, reviewable design documents. This skill converts unclear concepts into explicit YC-ready design documents that guide collaboration and decision making.

Core Features & Use Cases

  • Structured design docs for early-stage ideas and brainstorming sessions.
  • Phase 1 context gathering, goal alignment, and routing for plan reviews across Phase 2A/2B.
  • One-click generation of a plan with goals, constraints, stakeholders, success criteria, and a prioritized next steps list.

Quick Start

Describe your startup idea in a sentence and ask me to generate a YC-ready 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 turn a vague startup idea into a structured design doc?

To turn a vague startup idea into a structured design doc, provide a one-sentence concept description. The system converts ambiguous brainstorming sessions into explicit, review-ready documents featuring problem framing, scope, stakeholders, risks, and next steps.

What is the best way to prepare early-stage product explorations for a strategy review?

The best way to prepare early-stage product explorations for a strategy review is to generate a structured plan that aligns teams on goals, constraints, and success metrics. This process explicitly frames the problem and outlines prioritized next steps.

Can I use this to align my team on success metrics and constraints before building?

Yes, you can align your team on success metrics and constraints before building. The system outputs a structured plan that enforces a consistent formatting standard, ensuring all stakeholders understand the project scope, risks, and criteria.

What should a YC-ready design document include for early-stage founders?

A YC-ready design document for early-stage founders should include problem framing, scope, stakeholders, risks, and a prioritized next steps list. This structured output guides collaboration and decision-making during early product design.

Do I need a fully fleshed-out product design to generate a review-ready plan?

No, you do not need a fully fleshed-out product design to generate a review-ready plan. The system specializes in converting unclear, ambiguous concepts into explicit design documents through context gathering and goal alignment.

How does the context gathering process work for startup brainstorming sessions?

The context gathering process works by taking your initial idea description and routing it through a structured phase of goal alignment and plan reviews. This converts ambiguous brainstorming sessions into explicit, review-ready design documents.