office-hours

Stress-test product ideas by exposing demand gaps and unvalidated assumptions.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill office-hours-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/office-hours
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill office-hours-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams and builders from rushing into code before validating the problem, user demand, scope, and critical assumptions behind an idea.

Core Features & Use Cases

  • Structured Ideation: Run a focused office-hours session for startup, product, side-project, open-source, or hackathon ideas.
  • Assumption Testing: Ask six forcing questions covering demand reality, current alternatives, pain specificity, the narrowest wedge, user observation, and defensibility or sustainability.
  • Decision-Ready Planning: Produce an assumption challenge, biggest open question, design document, scope constraints, validation actions, and downstream handoff recommendations.
  • Use Case: Use this Skill when evaluating a new SaaS concept to identify the specific user, validate the status quo, define a two-week wedge, and determine what evidence is needed before engineering begins.

Quick Start

Ask the office-hours skill to stress-test your product idea before writing any code.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I validate a product idea before writing code?

Idea validation before coding requires stress-testing demand gaps, scope risks, and unvalidated assumptions via sequential questioning. This process generates a focused design document with scope constraints for downstream planning.

What questions should I ask to test startup ideation assumptions?

Startup ideation assumption testing uses six forcing questions covering demand reality, current alternatives, pain specificity, the narrowest wedge, user observation, and defensibility to expose critical scope risks before building.

Can I use an office hours session to define scope for a hackathon build?

Yes, an office hours session defines scope for hackathon builds. Builder mode applies assumption testing and context-aware questioning to narrow your wedge and identify validation actions for rapid prototyping.

Does idea validation work for side projects and personal automations?

Idea validation works for side projects and personal automations by applying assumption testing to identify the specific user, validate the status quo, and determine required evidence before development starts.

What deliverables should I expect from a product strategy stress-test?

A product strategy stress-test delivers an assumption challenge, biggest open question, focused design document, scope constraints, validation actions, and explicit downstream planning handoff recommendations.

When should I avoid rushing into building a SaaS concept?

Avoid building a SaaS concept with unvalidated demand assumptions. Stress-testing the specific user, current alternatives, and status quo prevents scope risks and ensures necessary evidence is gathered first.