office-hours

Generate structured YC office-hours design docs with required sections.

5|2|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/agatx/serenada --skill office-hours-agatx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/agatx/serenada --skill office-hours-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders and teams often craft chaotic, unstructured early-stage design notes. This skill guides them to generate YC-style office-hours design docs that articulate the problem, demand reality, and a plan for execution.

Core Features & Use Cases

  • Phase-driven prompts for Startup mode and Builder mode to produce a complete design doc.
  • Generates sections like Problem Statement, Demand Evidence, Status Quo, Target User, Narrowest Wedge, and Approaches, plus a handoff plan.
  • Supports both high-signal brainstorming and structured decision-making for quick alignment with mentors.

Quick Start

Draft a YC-style office-hours design doc for your idea in Startup or Builder mode.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I structure a YC office-hours design doc for my startup idea?

To structure a YC office-hours design doc, you need to generate phase-driven sections like Problem Statement, Demand Evidence, and Approaches. This skill guides founders through iterative questions to produce a handoff-ready artifact for both Startup and Builder modes.

What sections do I need for a handoff-ready startup design document?

A handoff-ready startup design document requires Problem Statement, Demand Evidence, Status Quo, Premises, and Approaches sections. The skill ensures all these required components are included and produces a phase-driven output artifact.

How do I turn unstructured early-stage ideas into an actionable design doc?

Turning unstructured ideas into an actionable design doc involves applying phase-driven prompts in Startup or Builder mode. The skill guides you through iterative questions to articulate the problem, demand reality, and execution plan for quick mentor alignment.

Can I use this design doc skill for both startup mode and builder mode?

Yes, you can use this design doc skill for both Startup mode and Builder mode. It applies phase-driven prompts to each context, guiding you to generate a complete YC-style office-hours design document with a handoff plan.

What is the best way to prepare for YC office hours with my team?

The best way to prepare for YC office hours is to draft a structured design doc covering your Problem Statement, Demand Evidence, and Narrowest Wedge. This skill supports high-signal brainstorming and structured decision-making for quick alignment with mentors.

When do I need to generate a phase-driven design artifact instead of a standard note?

You need to generate a phase-driven design artifact instead of a standard note when you require a handoff-ready output for mentor alignment. It transforms chaotic early-stage design notes into a structured YC-style document with clear premises and approaches.