office-hours

Create Phase 1 context-gathering plans with goals, constraints, and stakeholder questions.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/zzxtbeta/design-handbook --skill office-hours-zzxtbeta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/office-hours
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill office-hours-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YC-style office hours are notoriously hard to scale. This skill provides a structured, repeatable design-doc workflow that turns vague ideas into concrete, testable plans and artifacts that a team can execute against.

Core Features & Use Cases

  • Provides a phased, context-focused framework for brainstorming and requirement gathering.
  • Produces actionable design docs, with clear goals, questions, and success criteria for startup, intrapreneurship, or hackathon contexts.
  • Guides facilitators through a disciplined AskUserQuestion workflow to surface real user needs and risks.

Quick Start

Provide a Phase 1 context-gathering plan for the project and outline the next actionable questions for the team.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I turn vague startup ideas into concrete design docs?

To turn vague ideas into concrete design docs, you need a structured context-gathering plan that captures project goals, constraints, and stakeholders. This approach outlines actionable questions and required artifacts to surface real user needs and risks.

What is the best way to structure brainstorming sessions for hackathons or intrapreneurship projects?

Structuring brainstorming sessions for hackathons or intrapreneurship requires a phased, context-focused framework. This method guides facilitators through a disciplined questioning workflow to produce actionable design documents with clear success criteria.

How do I gather project context and define goals for a new open-source initiative?

Gathering project context for open-source initiatives involves defining a Phase 1 plan that specifies required artifacts and guardrails. This structured office-hours workflow surfaces user needs by outlining concrete questions to test assumptions and identify risks.

Can I use a YC-style office hours framework to scale requirement gathering for my team?

Yes, you can scale YC-style office hours requirement gathering by applying a repeatable design-doc workflow. This provides a structured AskUserQuestion process that transforms brainstorming into testable plans and artifacts a team can execute against.

What questions should I ask during context-gathering for startup design sessions?

During context-gathering for startup design sessions, you should ask questions that surface real user needs, clarify constraints, and identify project risks. The goal is to capture stakeholder requirements and translate them into actionable next steps.