office-hours

Guide product coaching sessions that reframe ideas into structured design documents.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill office-hours-0xharbs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/office-hours
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill office-hours-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reframes rough product ideas into a structured, actionable design doc that downstream skills (/plan, /dev, /qa) can consume.

Core Features & Use Cases

  • Phase-driven coaching: gather context, select mode (startup or builder), ask structured questions, perform a premise challenge, generate design alternatives, and produce a formal design document.
  • Design doc authoring: outputs a .context/designs entry with a clear problem statement, target user, core premises, chosen approach, scope, and success criteria.
  • Session orchestration: provides a repeatable workflow that helps teams surface pain, align on scope, and de-risk early product decisions.

Quick Start

Start a coaching session with /office-hours to initialize a design-doc flow for your project.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I turn rough product ideas into a structured design doc before coding?▼

Product coaching sessions guide teams through context gathering, premise challenges, and mode selection to produce a structured design document. This reframes rough ideas into actionable artifacts with clear problem statements, scope, and success criteria.

What is the best way to frame problems for early-stage products or hackathon projects?▼

Problem framing for early-stage products uses a phase-driven workflow that surfaces pain points and aligns stakeholder scope. It applies structured questions and alternative generation to de-risk decisions before any development begins.

How do I start a design doc coaching session for my project?▼

Start a coaching session by initializing the design-doc flow for your project. The workflow orchestrates context gathering, mode selection between startup or builder, and structured questioning to produce a formal design document.

Does this design doc workflow write code or generate planning artifacts?▼

The design doc workflow does not write code. It produces a shareable summary and a formal design artifact stored as a .context/designs entry, specifically formatted for consumption by downstream planning and development skills.

Can I use this for startup building as well as general product development?▼

Yes, the workflow supports both contexts through a mode selection phase. It allows you to choose between a startup mode and a builder mode to tailor the product coaching questions and design document output to your specific environment.

What limitations exist when generating design documents through product coaching?▼

This approach is limited to early-stage products and hackathon-style work needing disciplined problem framing. It focuses solely on producing design documents and does not execute code or handle downstream development tasks directly.