office-hours

Guide structured design sessions to produce action-oriented design documents.

107|19|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mr-daedalium/ostack --skill office-hours-mr-daedalium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/mr-daedalium/ostack/tree/main/office-hours
Command: npx skills add https://github.com/mr-daedalium/ostack --skill office-hours-mr-daedalium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, one-session-per-design-doc approach inspired by YC office hours to extract clear problem definitions, assumptions, and concrete next steps through a guided questioning protocol.

Core Features & Use Cases

  • Phase-based discovery: Phase 1 context gathering, Phase 2A startup mode if needed, Phase 2B builder mode for learning/hackathons, Phase 3 Premise Challenge, Phase 4 Alternatives, and plan-mode reviews.
  • Structured questioning: The Six Forcing Questions and AskUserQuestion prompts to elicit specific, evidence-based responses.
  • Output: A ready-to-use design doc detailing goals, constraints, decision criteria, and next steps.

Quick Start

Describe your project goal and ask me to run YC Office Hours to generate a 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 create a structured design doc for a startup project?

A structured design doc is produced through a guided questioning protocol that extracts problem definitions, assumptions, and next steps in a single session. It enforces a plan detailing goals, constraints, decision criteria, and assigned owners rather than implementation details.

What is the best way to run design-thinking sessions for pre-product ideas?

The best way to run design-thinking sessions for pre-product ideas is using a phase-based discovery method that adapts to your project stage. It targets startup or builder projects, prioritizing decision-quality and outputting an action-oriented plan with specific next actions.

How do I challenge project assumptions during a design review?

You challenge project assumptions during a design review by applying forcing questions and a premise challenge phase. This structured questioning elicits specific, evidence-based responses to ensure your design doc addresses concrete problems rather than untested hypotheses.

Can I use this design doc approach for hackathon or learning projects?

Yes, you can use this design doc approach for hackathon or learning projects by engaging builder mode. This specific phase is designed for learning environments and hackathons to help you quickly define goals, constraints, and next steps.

Does this design session generate code or implementation details?

No, this design session does not generate code or implementation details. It strictly enforces outputs as a plan including next actions, owners, and decision criteria to guide development, rather than providing the actual code implementation.