office-hours

Guides startup and side-project brainstorming through structured questions and generates design documents.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill office-hours-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/office-hours
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill office-hours-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump into building without validating demand, defining a narrow wedge, or stress-testing their assumptions. This Skill runs a structured office-hours session that challenges premises, forces specificity, and produces a reviewed design document. ## Core Features & Use Cases - Startup Mode Diagnostic: Six forcing questions covering demand reality, status quo, target user specificity, narrowest wedge, user observation, and future-fit, with pushback patterns against vague answers. - Builder Mode Brainstorm: Generative questions for side projects, hackathons, and open source ideas that surface the most exciting version of a concept. - Design Doc Generation: Writes a structured design document to the project directory and repo, then runs an adversarial reviewer subagent loop (up to 3 iterations) scoring completeness, consistency, clarity, scope, and feasibility. - Use Case: A founder with a vague idea like "an AI tool for developers" runs the session, gets pushed to name a specific user and a paid wedge, and walks away with an approved design doc ready for plan reviews. ## Quick Start Ask the assistant to run office hours to think through whether your new product idea is worth building.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I validate a startup idea before building it?

Run the office-hours session in startup mode. It asks six forcing questions about demand evidence, current workarounds, your specific target user, the narrowest paid wedge, observed user behavior, and future-fit, pushing back on vague answers until each is specific.

How to brainstorm a side project or hackathon idea?

Use builder mode, which asks generative questions about the coolest version of your idea, who you would show it to, and the fastest path to something usable. It ends with concrete build steps and a design doc rather than business validation tasks.

What output does the office-hours session produce?

It writes a structured design document covering problem statement, demand evidence, premises, approaches considered, and a recommended approach. The doc is saved to the project directory and, when in a git repo, to docs/designs for team review.

Does the design doc get reviewed before approval?

Yes. An independent reviewer subagent scores the document on completeness, consistency, clarity, scope, and feasibility across up to three iterations. Unresolved issues are persisted as Reviewer Concerns in the document.

When should I use office-hours versus going straight to planning?

Use it before any code exists, when exploring a concept or questioning whether something is worth building. It is designed to run before plan review skills so the design doc feeds downstream planning.