office-hours

Name: office-hours
Availability: InStock
Author: vibrationalforce

Generate Markdown design docs from user prompts via structured AskUserQuestion sessions.

Updated Oct 15, 2025

Search Tags:#phases #AskUserQuestion #design-doc #gstack #office-hours #builder-session

Ready to run

npx skills add https://github.com/vibrationalforce/Echoelmusic --skill office-hours-vibrationalforce

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

YC Office Hours provides a structured, repeatable process to transform vague ideas into concrete design documents by guiding hosts through evidence gathering, premise testing, and solution design, then exporting a ready-to-share document.

Core Features & Use Cases

Guided AskUserQuestion sessions that enforce one-question-at-a-time interrogation.
Phase-based workflow covering context gathering, premises challenge, and design doc generation for startup or builder scenarios.
Automatic generation of a formal design document with metadata like Supersedes and branch provenance.
Works for both Startup mode (Phase 2A) and Builder mode (Phase 2B), adapting prompts to the goal.

Quick Start

Describe your project goal and pick the mode you want (Startup or Builder) to begin an office-hours session.

Frequently Asked Questions about office-hours

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

FAQPage Schema

What is a structured design session for converting ideas into design docs?▼

A structured design session automates YC Office Hours-style brainstorming, guiding you through evidence gathering, premise testing, and solution design to output a concrete Markdown design document with versioning metadata.

How do I generate a design document from a project idea?▼

To generate a design document, describe your project goal and select Startup or Builder mode. An interactive AskUserQuestion flow enforces one-question-at-a-time interrogation across phases to produce the final Markdown file.

What is the difference between Startup mode and Builder mode for design brainstorming?▼

Startup mode (Phase 2A) and Builder mode (Phase 2B) adapt the interactive design session prompts to your specific goal, tailoring the premise testing and solution design workflow for either startup scenarios or side project builder scenarios.

Can I use interactive prompts to enforce one-question-at-a-time interrogation during design?▼

Yes, the AskUserQuestion-driven interactive flow strictly enforces one-question-at-a-time interrogation. This guided process ensures structured context gathering and premise testing across all five workflow phases.

How does versioning work for Markdown design documents?▼

Generated Markdown design documents include automatic versioning and supersession metadata, tracking branch provenance and recording Supersedes data to maintain a clear history of your design document iterations.

What are the limitations of automating YC Office Hours-style brainstorming?▼

This approach requires strict adherence to the Phase 1-5 pipeline and sequential AskUserQuestion interrogation. It is limited to generating Markdown design documents and does not produce other formats or skip workflow phases.