office-hours

Structure product ideation with forcing questions and design thinking workflows.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill office-hours-jia-hong-peng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill office-hours-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates unstructured guesswork when developing new product ideas, startup concepts, or side projects, giving you a proven framework to test if an idea is worth building before investing time in code.

Core Features & Use Cases

  • Startup Mode: Six forcing questions that expose real user demand, status quo pain points, your narrowest market wedge, and long-term future fit for early-stage startup ideas.
  • Builder Mode: Design thinking brainstorming for side projects, hackathons, learning projects, and open source tools, with automatic design doc generation to capture your plans.
  • Use Case: You have an idea for a new app that helps people learn English from YouTube videos. Use this Skill to run through the forcing questions to confirm there's real user demand before writing a single line of code.

Quick Start

Use the office-hours skill to validate your new startup idea or brainstorm a side project design.

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?▼

To validate a startup idea before coding, use structured forcing questions to expose real user demand, status quo pain points, and your narrowest market wedge to confirm long-term future fit.

What is the best way to brainstorm a side project or hackathon idea?▼

Brainstorming a side project or hackathon idea is best done using design thinking workflows to structure ideation, followed by automatic design doc generation to capture project plans before implementation.

How do I structure product ideation for open source tool scoping?▼

Structuring product ideation for open source tool scoping involves applying rigorous demand validation and design thinking workflows to define project scope and generate structured design documentation prior to development.

Can I generate design docs automatically from unstructured product ideas?▼

Yes, you can generate design docs automatically from unstructured product ideas by processing concepts through design thinking workflows that structure ideation and output formal documentation.

Does this approach work for early-stage startup planning without technical dependencies?▼

This approach works for early-stage startup planning without technical dependencies by relying on forcing questions and design thinking to validate demand and document the wedge before any code is written.