office-hours

Guide structured questioning to surface demand reality and generate a design doc.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill office-hours-tyhuffman7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-office-hours
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill office-hours-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams brainstorm and plan bold product ideas by guiding structured questions that surface demand reality, risky assumptions, and actionable next steps. It provides two modes: Startup mode with six forcing questions to expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit; Builder mode for design thinking brainstorming on side projects, hackathons, learning, and open source. It saves a design doc that captures decisions, scope, and rationale.

Core Features & Use Cases

  • Startup mode forces structured thinking to surface riskiest assumptions.
  • Builder mode enables design-thinking brainstorming for side projects, hackathons, learning, and open source.
  • Proactive invocation before plan reviews to shape strategy and produce a design doc.
  • Generates a concise design doc that documents rationale, scope, decisions, and next steps.

Quick Start

Describe your product idea and I will run the office-hours skill to brainstorm options and draft a design doc.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I brainstorm and plan bold product ideas for a startup?

To structure product planning, you must surface demand reality, current constraints, and future-fit opportunities. This approach guides ideation by forcing teams to question risky assumptions and define the narrowest wedge for initial market entry.

What is the best way to document design decisions and rationale for internal projects?

Document design decisions by generating a design doc that captures scope, rationale, and next steps. This ensures team alignment by recording the structured questioning outputs and future-fit opportunities identified during planning reviews.

Can I use design thinking brainstorming for side projects and hackathons?

Yes, Builder mode enables design thinking brainstorming specifically for side projects, hackathons, and open source work. It applies structured questioning to surface actionable next steps for internal projects and learning initiatives.

Does product planning work with proactive invocation before plan reviews?

Yes, proactive invocation before plan reviews shapes strategy by surfacing current constraints and future-fit opportunities. This process produces a design doc capturing rationale, scope, and next steps for the planning review.

What questions help surface demand reality and risky assumptions for new product ideas?

Six forcing questions expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. These questions surface risky assumptions and actionable next steps during new product idea brainstorming.