office-hours

Guides structured brainstorming sessions that interrogate startup ideas and produce design docs.

Updated May 15, 2026
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill office-hours-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/office-hours
Command: npx skills add https://github.com/tgmarinho/canetaco --skill office-hours-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often jump into code before validating whether an idea has real demand. This Skill runs a structured YC-style office hours session that stress-tests product ideas with forcing questions before any code is written, and saves the outcome as a design doc. ## Core Features & Use Cases - Startup Mode: Six forcing questions that expose demand reality, status quo alternatives, desperate specificity, the narrowest wedge, observation, and future-fit of a startup idea. - Builder Mode: Design-thinking brainstorming for side projects, hackathons, learning projects, and open source work. - Design Doc Output: Saves the session outcome as a design document for later reference and planning. - Use Case: You have an idea for a WhatsApp-first e-signature product. Invoke the skill, answer the forcing questions about who desperately needs it and what they do today, and walk away with a design doc ready for /plan-ceo-review or /plan-eng-review. ## Quick Start Ask the assistant to run office hours on your new product idea and answer the forcing questions it poses.

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 writing code?

Run an office hours session that asks six forcing questions covering demand reality, the status quo alternative, desperate specificity, the narrowest wedge, observation, and future-fit. The session ends with a saved design doc you can feed into planning reviews.

What is the difference between startup mode and builder mode?

Startup mode applies YC-style forcing questions to test whether a business idea has real demand. Builder mode uses design-thinking brainstorming for side projects, hackathons, learning, and open source work where demand validation matters less.

When should I use office hours versus a planning review?

Use office hours first, when the idea is still unformed and no code exists. Its description explicitly says to run it before /plan-ceo-review or /plan-eng-review, which evaluate a concept that has already been thought through.

Does office hours work for non-startup side projects?

Yes. Builder mode is designed for side projects, hackathons, learning exercises, and open source work. It uses design-thinking brainstorming rather than demand-validation questions.

What does office hours produce at the end of a session?

It saves a design doc capturing the session outcome. Prior sessions and design docs are loaded as context in later invocations, so the skill builds on your project history over time.