office-hours

Pressure-test new product ideas and produce a structured design doc.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill office-hours-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/office-hours
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill office-hours-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you figure out whether a new idea is worth building before you waste time on the wrong thing. It pushes past vague excitement and forces clarity on demand, users, wedge, and next steps.

Core Features & Use Cases

  • Startup pressure-testing: Ask the hard questions that expose whether there is real demand, a painful status quo, and a narrow first customer.
  • Builder brainstorming: Turn a rough side project, hackathon concept, or open source idea into a practical design direction and a written plan.
  • Decision support: Produce a design doc that captures tradeoffs, scope, and what to do next when the idea still needs shape.

Quick Start

Ask this skill to help you think through a new product idea, then answer its questions so it can produce 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 pressure-test startup ideas before writing any code?

To pressure-test startup ideas before building, you need guided questioning that exposes real demand, a painful status quo, and a narrow first customer. This approach forces clarity on users and wedge, turning vague excitement into a structured decision before development.

What is the best way to turn side project brainstorming into a design doc?

The best way to turn side project brainstorming into a design doc is through structured decision support that captures tradeoffs, scope, and next steps. This process transforms rough hackathon concepts into a practical design direction and a written plan.

Can I use this to evaluate hackathon concepts and open source ideas?

Yes, you can evaluate hackathon concepts and open source ideas by applying targeted feasibility questions. This pressure-testing method helps determine whether there is real demand before you commit time to building the project.

How do I validate product strategy and demand for a new project?

To validate product strategy and demand for a new project, ask hard questions that expose whether a painful status quo exists and identify a narrow first customer. This forces clarity on the wedge and ensures your idea is worth building.

Does this feasibility analysis work for learning projects without a commercial target?

Yes, feasibility analysis works for learning projects by forcing clarity on scope, tradeoffs, and next steps. Even without a commercial target, pressure-testing helps shape the idea into a practical design direction before you start coding.

When should I avoid pressure-testing a new product idea?

You should avoid pressure-testing a new product idea if you cannot articulate a rough concept or target user to answer guided questions. The process requires initial brainstorming input to evaluate demand and generate a structured design doc.