office-hours

Name: office-hours
Availability: InStock
Author: tiosavich

Guide founders through structured office-hours sessions to produce Markdown design docs.

Updated Sep 10, 2024

Search Tags:#startup #design-doc #design-thinking #builder-mode #gstack #office-hours

Ready to run

npx skills add https://github.com/TioSavich/UMEDCTA --skill office-hours-tiosavich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill office-hours-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? YC Office Hours provides a structured process to convert fuzzy product ideas into a concrete design doc through guided questions and a two-mode framework (startup and builder). This ensures a traceable, reviewable artifact that can be handed off to teammates.

## Core Features & Use Cases

Guided, phase-based office hours that produce a complete design document.
Supports two modes: Startup (plan CEO review) and Builder (rapid brainstorming for side projects).
Produces a shareable Markdown design doc with sections for problem, constraints, user, and success criteria.

### Quick Start Run the office-hours flow to generate a draft design doc by answering the guided questions 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 turn startup ideas into a structured design doc?▼

To turn startup ideas into a design doc, you can use a guided office-hours flow that asks structured questions and outputs a Markdown file. This process converts fuzzy concepts into a tangible artifact with problem statements and success criteria.

What is the difference between startup mode and builder mode for product ideation?▼

Startup mode structures ideation for CEO review and planning, while builder mode enables rapid brainstorming for side projects. Both modes produce a shareable Markdown design doc containing the problem, constraints, and user definitions.

How do I create a design document with problem statements and success criteria?▼

You create a design document by answering phase-driven prompts during a guided session. The automated writer then generates Markdown formatted with specific sections for the problem statement, constraints, user, and success criteria.

Can I use this guided design-thinking session for side projects?▼

Yes, you can use builder mode specifically for side projects and rapid brainstorming. It applies the same structured design-thinking methodology to generate a concrete design doc artifact for your ideation process.

What format does the automated design doc writer output?▼

The automated design doc writer outputs Markdown. It uses YAML frontmatter metadata and phase-driven prompts to generate a reviewable and shareable file containing your problem statement and success criteria.