office-hours

Creates actionable design documents from office-hours brainstorming sessions.

Updated Aug 27, 2026

Search Tags:#brainstorming #idea validation #design docs #product strategy #startup #founder coaching

Ready to run

npx skills add https://github.com/abrahamgreyson/skills --skill office-hours-abrahamgreyson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/abrahamgreyson/skills/tree/main/gstack/office-hours
Command: npx skills add https://github.com/abrahamgreyson/skills --skill office-hours-abrahamgreyson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you figure out whether a new idea is worth building by turning vague excitement into concrete demand, scope, and wedge questions.

Core Features & Use Cases

Runs a structured founder interview that tests demand reality, current alternatives, urgency, and the narrowest viable wedge.
Supports two modes: startup idea exploration for early concepts and builder brainstorming for side projects, hackathons, learning, and open source.
Produces a durable design document and hands it off to downstream review skills so the conversation becomes an actionable plan.
Example: use it when you have a promising idea but need help deciding whether to pursue it, refine it, or drop it.

Quick Start

Ask the office-hours skill to pressure-test my new product idea and save the resulting 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 validate a startup idea before writing any code?▼

Product idea validation involves testing demand reality, current alternatives, and urgency through forced-question probing. This skill guides you through structured brainstorming to determine whether to pursue, refine, or drop your concept before any code is written.

What's the best way to structure brainstorming for an early-stage product concept?▼

Structured brainstorming for an early-stage product concept uses a founder interview format with forced-question probing and branch-aware context gathering. This process turns vague excitement into concrete scope and wedge questions, producing a design doc for downstream review.

Can I use this for side project and hackathon brainstorming instead of a startup?▼

Yes, you can use the builder brainstorming mode for side projects, hackathons, learning, and open source concepts. It applies the same structured interview and design-doc creation process without requiring a full startup strategy commitment.

How do I create a design document from an open-ended product discussion?▼

Creating a design document from an open-ended product discussion requires branch-aware context gathering and forced-question probing. This skill synthesizes the conversation into a durable design doc and hands it off to downstream review skills as an actionable plan.

Does idea validation work for go-or-no-go decisions on existing startup concepts?▼

Idea validation works for go-or-no-go decisions by applying founder rigor to test demand reality and the narrowest viable wedge. It helps you decide whether to pursue, refine, or drop an existing startup concept before committing development resources.

When should I avoid using a structured founder interview for product strategy?▼

You should avoid using a structured founder interview when you already have a validated design doc and need implementation, or if your project requires coding immediately without prior scope definition, as this skill focuses strictly on pre-code validation and strategy.