office-hours

Guide raw ideas through six forcing questions to produce sharpened problem statements.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill office-hours-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/office-hours
Command: npx skills add https://github.com/misty-step/volume --skill office-hours-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform raw ideas into sharpened problem statements by guiding users through Gary Tan's six forcing questions, preventing premature scoping and misdirected work.

Core Features & Use Cases

  • Structured interrogation: follow the six questions in order to surface demand reality, current status quo, desperate specificity, the narrowest wedge, what we would learn, and future-fit viability.
  • Pre-shape guidance: outputs a sharpened problem statement ready for /shape or related validation steps.
  • Broad applicability: useful for startups, product teams, and innovators who start with fuzzy backlog items or vague goals.

Quick Start

Provide a raw idea and run the six forcing questions to produce a sharpened 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 sharpen a fuzzy product idea into a testable problem statement?

Six forcing questions provide a structured interrogation method to transform raw ideas into sharpened problem statements. By sequentially addressing demand reality, status quo, and desperate specificity, this framework prevents premature scoping and clarifies the actual problem before development begins.

What is the best way to validate demand reality for an early-stage startup idea?

The best way to validate demand reality is using a structured ideation framework that forces teams to define the current status quo and identify desperate specificity. This interrogation surfaces explicit demand evidence, ensuring the backlog item has a testable outcome before scoping begins.

How do I prepare a raw backlog item for the shape phase?

To prepare a raw backlog item for the shape phase, apply six forcing questions to extract a sharpened problem statement. This pre-shape guidance enforces testable outcomes and explicit demand reality evidence, ensuring the item is sufficiently defined for the subsequent shaping process.

Can I use forcing questions for product management tasks outside of startups?

Forcing questions are broadly applicable for product management tasks outside of startups, extending to any product team with fuzzy backlog items. The framework scales across different contexts to interrogate what we would learn and establish future-fit viability before committing development resources.

Why does my product team struggle with premature scoping on vague goals?

Product teams struggle with premature scoping on vague goals because they skip structured interrogation of demand reality and current status quo. Without forcing questions to establish desperate specificity, teams risk misdirected work on raw ideas that lack explicit demand evidence and testable outcomes.