office-hours

Turn rough startup or builder ideas into a structured design document with a concrete next action.

8|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/MFS-code/gstack --skill office-hours-mfs-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/MFS-code/gstack/tree/main/office-hours
Command: npx skills add https://github.com/MFS-code/gstack --skill office-hours-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you clarify what you’re actually building and why before any implementation starts, so you can produce a usable product/design direction instead of vague brainstorming.

Core Features & Use Cases

  • YC-style product diagnostic: In startup/intrapreneurship mode, it forces demand reality, status-quo comparison, and a narrow wedge so you can validate the core before shipping.
  • Builder-mode design partnering: In hackathon/open-source/learning mode, it sharpens delight, audience, and the fastest shippable version to create something you can show or share.
  • Design-doc output focus: It produces a structured design doc (not code) and ends with a concrete “what to do next” assignment based on your answers.

Quick Start

Invoke office-hours when you want help thinking through an idea or deciding if it’s worth building, such as when you say “office hours” or you ask “help me think through this.”

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I turn rough startup ideas into a structured design document?

To turn rough startup ideas into a structured design document, you can trigger a guided brainstorming session that forces demand reality and status-quo comparison. This process outputs a design doc with a concrete next action instead of vague concepts.

What is the best way to validate product demand before building?

Validating product demand before building involves running a YC-style diagnostic to force demand reality and identify a narrow wedge. This startup diagnostic clarifies your core value proposition before any implementation starts.

How do I plan next steps for a side project or hackathon idea?

Planning next steps for a side project or hackathon idea requires builder-mode design partnering that sharpens audience focus and identifies the fastest shippable version. It ends by assigning a concrete action based on your answers.

Does this product validation process output code or design guidance?

This product validation process outputs design guidance rather than code. It restricts output strictly to a structured design document and a clear next-step assignment to ensure you clarify what you are building before implementation.

Can I use this for brainstorming open-source and learning projects?

You can use this for brainstorming open-source and learning projects through its builder-mode functionality. It sharpens the project's delight factor and audience targeting to help you create something you can easily show or share.

When do I need a design document for product ideation?

You need a design document for product ideation when you want to clarify what you are actually building and why before any implementation starts. It transforms vague brainstorming into a usable product direction with a concrete next action.