office-hours

Guide teams through structured product discovery and generate a design-doc.md.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Wilder1222/superomni --skill office-hours-wilder1222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/Wilder1222/superomni/tree/main/skills/office-hours
Command: npx skills add https://github.com/Wilder1222/superomni --skill office-hours-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through structured product discovery and validation before building, ensuring the problem is well understood, demand is real, and the right design doc is produced.

Core Features & Use Cases

  • Dual modes: Startup mode for validating real-market demand with six forcing questions, and Builder mode for design thinking on side projects, open source, or personal tools.
  • Design doc generation: Produces a design-doc.md capturing problem statements, user insights, scope, and success criteria to align stakeholders.
  • Mode-driven workflow: Assists with framing, challenge-and-reframe, and artifact creation, then auto-outputs a complete plan ready for review.

Quick Start

Choose Startup or Builder mode to begin the forcing questions, then generate and save a design-doc.md.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I validate startup product demand before building?

Product discovery validates real market demand through structured questions before development. It applies startup forcing questions to verify problem statements, ensuring real demand signals exist and preventing premature building.

What is the best way to create a design doc for early product discovery?

Creating a design doc for product discovery involves generating a design-doc.md capturing problem statements, user insights, scope, and success criteria. This aligns stakeholders and documents progress before building begins.

Can I use design thinking for side projects and open-source initiatives?

Yes, design thinking applies to side projects and open-source initiatives via Builder mode. It guides personal tools through framing, challenge-and-reframe workflows, and artifact creation to validate ideas before building.

How do I guide my team through product discovery and validation?

Guide teams through product discovery using a mode-driven workflow applying framing, challenge-and-reframe techniques, and artifact creation. This enforces structured questions and outputs a complete session artifact documenting progress and decisions.

What is the difference between Startup mode and Builder mode for product discovery?

Startup mode validates real-market demand using six forcing questions, while Builder mode applies design thinking to side projects, open source, or personal tools. Both modes produce a design-doc.md and complete session artifact.

Do I need a design doc to start product validation?

You do not need a pre-existing design doc to start product validation; the workflow generates one. It guides you through structured questions and then outputs a design-doc.md capturing validated scope, user insights, and success criteria.