# /office-hours: Pressure-test an idea before your agent writes any code

Source: https://trendhub.net/skills/garrytan-gstack/office-hours
Skill folder: https://github.com/garrytan/gstack/tree/main/office-hours
Pack: gstack (https://trendhub.net/skills/garrytan-gstack)
Works with: Claude Code, Claude Code (team mode for a shared repo), Codex, Cursor, OpenCode, Gemini CLI and other agents

Office hours casts the agent as a startup advisor who questions the problem before any solution. It sorts you into startup or builder mode, asks hard questions one at a time, challenges the premises, offers two or three approaches with effort and risk, and ends with a design document plus a concrete next action. Later planning skills read that document.

## When to use it

- You have a product idea and are not sure it is the right problem to solve.
- You are about to start a feature and want the scope and approach agreed first.
- You want a written design doc that plan reviews and QA can build on.

## How it works

1. **Gather context**: The agent reads CLAUDE.md, TODOS.md and recent git history, lists earlier design docs and asks what your goal is.
2. **Question by mode**: Startup and internal projects get a diagnostic of forcing questions; hackathons, learning and side projects get a brainstorming partner.
3. **Challenge premises**: It states the premises behind the idea and asks you to agree or disagree with each before moving on.
4. **Compare approaches**: It lays out at least a minimal option and an ideal-architecture option with effort, risk, pros and cons, then waits for your pick.
5. **Write the design doc**: After approval it records the decisions, the signals it noticed and a real-world assignment for you.

## What it steers the agent away from

- Writing code or scaffolding during the planning session.
- Batching several questions into one prompt.
- Searching the web with your stealth product name instead of general category terms.

## What it can touch

Reads the repo and git history, may run web searches after asking you, and writes a design doc and session notes under gstack's state folder.

## Pairs well with

- `/autoplan`
- `/plan-ceo-review`
- `/plan-eng-review`

## Questions

### What if I already have a full plan?

It skips the questioning phase but still challenges the premises and makes you compare alternatives before writing the doc.

### Does it share my idea with search engines?

Only after you agree, and it searches generalised category terms rather than your product name or concept.
