office-hours

Creates formal design documents using phased Yandex-style Office Hours methodology without code.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill office-hours-leessju
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/leessju/claude-skills/tree/main/office-hours
Command: npx skills add https://github.com/leessju/claude-skills --skill office-hours-leessju

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines early-stage product work by ensuring teams build a clear problem frame and a formal design document before coding, using a disciplined, one-question-at-a-time diagnostic process.

Core Features & Use Cases

  • Phase-driven discovery workflow (Phases 1–6) that culminates in a ready-to-share design document without writing code.
  • Evidence-first interrogation that pushes for specific, testable commitments and a concrete next action.
  • Flexible modes (Startup mode for diagnostic rigor; Builder mode for design-partner exploration) to fit different goal settings.

Quick Start

Begin Phase 1 by clarifying the goal and collecting context; proceed through Phases 2–6 with one-question-at-a-time prompts until a final design document is produced.

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 design doc for product discovery before writing code?▼

Use a phased diagnostic workflow to frame problems and produce a structured design document for product discovery before coding. It guides you through six phases, interrogating evidence and premises one question at a time to finalize scope and next actions without writing software.

What is the YC Office Hours methodology for startup product validation?▼

The YC Office Hours methodology for startup product validation uses a one-question-at-a-time diagnostic process. It forces teams to assemble evidence, define premises, and explore alternatives across six phases to validate demand and feasibility before building.

How do I validate demand and feasibility for a startup idea without coding?▼

Validate demand and feasibility for a startup idea without coding by running a disciplined diagnostic process. It pushes for specific, testable commitments and evidence-first interrogation, ending with a concrete next action and a ready-to-share design document.

Can I use this design doc workflow for intrapreneurship projects inside a company?▼

Yes, this design doc workflow applies to intrapreneurship projects inside a company. It offers flexible modes, including a Startup mode for diagnostic rigor and a Builder mode for design-partner exploration, fitting various goal settings.

What is the best way to structure a phased diagnostic for early-stage product work?▼

The best way to structure a phased diagnostic for early-stage product work is a six-phase discovery workflow. It starts by clarifying goals and collecting context, then proceeds through one-question-at-a-time prompts until a final design document is produced.

Why does my team need a formal design document before starting software development?▼

Your team needs a formal design document before starting software development to ensure a clear problem frame. It streamlines early-stage product work by enforcing a disciplined interrogation of scope, alternatives, and premises, preventing premature development.