office-hours

Guide product teams through six forcing questions to validate feature ideas.

60|9|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/mvschwarz/openrig --skill office-hours-mvschwarz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/pm/office-hours
Command: npx skills add https://github.com/mvschwarz/openrig --skill office-hours-mvschwarz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC-style product advisor framework to pressure-test feature ideas using a structured six-question method, ensuring there is real demand, a clear wedge, and evidence before committing to build.

Core Features & Use Cases

  • Six forcing questions (Demand Reality, Status Quo, Desperate Specificity, Narrowest Wedge, Observation / Surprise, Future-Fit) guide evidence-backed validation.
  • Step-by-step process: capture pitches, summarize after each answer, and rate strength (Strong / Needs Work / Red Flag).
  • Output a validation report saved as validation.md and structured for downstream requirements and executives.

Quick Start

Describe the feature idea in 2-3 sentences to start the validation.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I validate feature ideas with evidence before committing to build?

Feature idea validation uses a structured six-forcing-questions framework to assess demand, wedge potential, and evidentiary backing. Teams capture pitches, answer each question, rate response strength, and output a validation report to ensure there is real demand before building.

What is the forcing questions method for product demand validation?

The forcing questions method for demand validation applies six specific tests: Demand Reality, Status Quo, Desperate Specificity, Narrowest Wedge, Observation or Surprise, and Future-Fit. Each question pressure-tests early-stage product concepts to ensure evidence-backed validation.

How do I run structured demand validation for early-stage SaaS features?

Structured demand validation for SaaS features runs through a step-by-step process: describe the feature idea, answer the six forcing questions, summarize after each answer, and rate strength as Strong, Needs Work, or Red Flag to enforce evidence-based product management.

Does this feature idea validation framework work for consumer applications?

Feature idea validation applies to early-stage product concepts across both SaaS and consumer applications. The six-question assessment framework evaluates demand reality and narrowest wedge potential regardless of the specific application type.

What format does the idea assessment validation report output?

The idea assessment validation report outputs as a structured validation.md file. This report is suitable for downstream clarity and decision-making, documenting evidence and strength ratings for requirements and executive review.

When should I not use evidence-based validation for feature ideas?

Evidence-based validation for feature ideas is not suited for concepts lacking enough context for a 2-3 sentence pitch description. The framework requires documented evidence for each of the six forcing questions to properly assess demand reality and wedge potential.