office-hours

Evaluate product ideas with forcing questions and generate design documentation.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill office-hours-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/office-hours
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill office-hours-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founders and builders often waste time developing products that lack real market demand, or struggle to structure unstructured brainstorming sessions for new ideas, side projects, and hackathon entries. This skill eliminates that guesswork by providing a proven YC-style framework to evaluate idea viability before any code is written.

Core Features & Use Cases

  • Dual-mode workflow: Switch between Startup Mode for new product validation and Builder Mode for side project, hackathon, and open source brainstorming.
  • Forcing questions: Startup Mode uses six targeted questions to expose demand reality, status quo pain points, narrow market wedges, and future-fit potential for new ideas.
  • Design documentation: Automatically saves a structured design doc for every session, so you can reference decisions and insights later.
  • Use case example: If you have an idea for an AI-powered scheduling tool for freelance designers, use this skill to walk through the forcing questions to confirm there's real demand before building a prototype, or brainstorm features for a hackathon project in under 30 minutes.

Quick Start

Use the office-hours skill to evaluate your new idea for a freelance designer scheduling tool to determine if it's worth building and generate a design doc for the project.

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 demand for a new product idea before writing code?

Startup demand validation uses forcing question frameworks to evaluate idea viability, expose demand reality, and identify narrow market wedges before development begins.

Can I use design thinking to brainstorm features for a hackathon project?

Yes, design thinking workflows structure unstructured brainstorming sessions for hackathon planning, side project design, and open source scoping work to generate actionable design documentation.

What is the best way to scope a side project to avoid building unviable concepts?

Side project planning applies targeted forcing questions to confirm market demand and identify status quo pain points, ensuring you avoid investing time in unviable concepts before any development work begins.

Does this YC office hours framework support generating design documentation for future reference?

Yes, the YC office hours framework automatically saves a structured design doc for every evaluation session, allowing you to reference decisions and insights later.

When should I not use startup validation workflows for idea brainstorming?

Startup validation workflows are not suited for projects already past the demand validation stage, as they focus entirely on pre-development forcing questions and market wedge identification rather than execution.