office-hours

Guide startup teams through design discussions and generate a formal design doc.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill office-hours-ulanxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/Ulanxx/mzstack/tree/main/office-hours
Command: npx skills add https://github.com/Ulanxx/mzstack --skill office-hours-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides startup teams and builders through structured design discussions and outputs a shareable design doc that records decisions, assumptions, and next steps.

Core Features & Use Cases

  • Guided office-hours prompts that push for specificity and evidence.
  • Automatic generation of a multi-section design doc capturing problem, scope, decisions, risks, and next actions.
  • Use cases include early-stage startup idea evaluation, feature scoping, and internal project planning with stakeholders.

Quick Start

Describe your startup idea and run the office-hours flow to generate a comprehensive 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 create a design doc for a startup idea evaluation?▼

To create a design doc for a startup idea evaluation, use guided office-hours prompts that push for specificity and evidence, automatically generating a multi-section document capturing the problem, scope, decisions, risks, and next actions.

What is the best way to document product management decisions for feature scoping?▼

The best way to document product management decisions for feature scoping is through structured design conversations that produce a formal design doc, recording assumptions, scope, and an action plan to ensure evidence-driven alignment.

How do structured design conversations improve internal R&D project planning?▼

Structured design conversations improve internal R&D project planning by guiding startup teams through focused, evidence-driven discussions that clarify the problem space and output a shareable document with clear next steps for stakeholders.

Can I use office-hours prompts for intrapreneurship projects with multiple stakeholders?▼

Yes, you can use office-hours prompts for intrapreneurship projects with multiple stakeholders, applying collaborative prompts and structured note-taking to ensure consistent outputs and formal design documentation.

Do I need collaborative note-taking to generate startup design documentation?▼

Yes, you need collaborative note-taking during the office-hours flow to ensure consistent outputs, as the process relies on guided prompts and structured input to generate a comprehensive design doc.