office-hours

Run YC-style office hours to reframe feature requests and generate design docs.

1|1|Updated Mar 31, 2026

Search Tags:#startup #design-doc #design-thinking #reframe #problem-framing #office-hours

Ready to run

npx skills add https://github.com/putrawitama/DenchClaw --skill office-hours-putrawitama

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You run YC-style office hours to uncover the real problem behind a feature request, reframing it before any code is written and capturing a design doc for downstream review.

Core Features & Use Cases

Mode detection to categorize sessions as Startup or Builder.
Six Forcing Questions to surface truth, including Demand Reality, Status Quo Challenge, Desperate Specificity, Narrowest Wedge, Observation, and Future-Fit.
Output REFRAME summaries and a structured Design Doc to feed plan-ceo-review and plan-eng-review.
Builder Mode prompts for design thinking and fast, demo-driven iterations for side projects or hackathons.
Save and reuse a reusable session template to accelerate future sessions.

Quick Start

Initiate an office-hours session by asking the six forcing questions one at a time and produce a reframed problem statement.

Frequently Asked Questions about office-hours

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

FAQPage Schema

How do I reframe a feature request before writing any code?▼

To reframe a feature request before coding, run a YC-style office-hours session using six forcing questions to uncover the real problem. This process produces a REFRAME summary and a structured Design Doc for downstream plan reviews.

What is YC-style office hours for problem framing in product management?▼

YC-style office hours for problem framing is a structured questioning process that identifies the real problem behind a feature request. It applies Startup and Builder modes to challenge assumptions and generate a reframed problem statement.

How do I write a design doc for downstream engineering and CEO plan reviews?▼

Generate a design doc for plan reviews by first running office-hours sessions to surface demand reality and narrowest wedge. The output is a structured Design Doc saved to the workspace, preparing inputs for plan-ceo-review and plan-eng-review.

Can I use design thinking to validate side project or hackathon ideas?▼

Yes, you can validate side project or hackathon ideas using Builder Mode. It prompts for design thinking and fast, demo-driven iterations to quickly surface the real problem and reframe your idea before committing to development.

What are the six forcing questions to surface the real problem behind a feature?▼

The six forcing questions to surface the real problem include Demand Reality, Status Quo Challenge, Desperate Specificity, Narrowest Wedge, Observation, and Future-Fit. They are asked one at a time during an office-hours session.

Does office-hours support saving reusable session templates for future product reviews?▼

Yes, office-hours supports saving and reusing a session template. This allows you to accelerate future product review sessions by applying the same YC-style problem framing and design doc generation workflow.