office-hours

Generate design docs from brainstorming sessions with phased questioning.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill office-hours-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/office-hours
Command: npx skills add https://github.com/timurgaleev/vibestack --skill office-hours-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates disciplined design docs from brainstorming sessions to ensure the problem is understood before crafting solutions.

Core Features & Use Cases

  • Phase-driven Q&A workflow that guides users from context gathering through Premise Challenge to final design alternatives.
  • Phase-aware prompts and one-question-at-a-time interactions that surface concrete, evidence-based insights.
  • Supports optional landscape awareness and a cross-model second opinion to challenge premises and sharpen direction.

Quick Start

Describe your goal and I will generate a design doc outlining the problem and plan.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I turn brainstorming sessions into structured design docs?

You can generate disciplined design docs from brainstorming by running a phase-driven Q&A workflow that ensures the problem is fully understood before crafting solutions. The process moves through context gathering, premise challenge, and final design alternatives.

What is the best way to challenge design premises before committing to a solution?

Challenging design premises involves a phase-driven questioning process that surfaces concrete, evidence-based insights. Optional landscape awareness and cross-model second opinions can be applied to test assumptions and sharpen the final direction.

How do I write a design doc that properly outlines alternatives?

Writing design docs with concrete alternatives requires a guided brainstorming process starting with context gathering. The workflow progresses through phase-aware prompts to evaluate premises and ultimately deliver structured design alternatives.

Can I use a phased questioning process to understand a problem before coding?

A phased questioning process works effectively to understand problems before coding by guiding users through four distinct phases. This ensures one question is addressed at a time, moving from initial context gathering to a final structured design doc.

Does guided brainstorming work for startup and builder modes?

Guided brainstorming explicitly supports both startup and builder modes to generate design docs. The phase-aware workflow adapts questioning to suit each mode, ensuring premises are challenged before delivering structured alternatives.

When do I need landscape awareness during design doc generation?

Landscape awareness is needed when you want to contextualize your design alternatives against existing solutions during brainstorming. It serves as an optional step to challenge premises and sharpen the direction of your final design doc.