office-hours

Guide brainstorming, strategy, and design thinking for product development.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/GrassHopper42/ANTidy --skill office-hours-grasshopper42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-hours
Source: https://github.com/GrassHopper42/ANTidy/tree/main/.claude/skills/gstack/office-hours
Command: npx skills add https://github.com/GrassHopper42/ANTidy --skill office-hours-grasshopper42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gstack, git, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The office-hours Skill addresses the challenges of brainstorming, strategy, and design thinking for product development. It helps users think through concepts, validate ideas, and make informed decisions.

Core Features & Use Cases

  • Brainstorming Sessions: Facilitates brainstorming sessions for side projects, hackathons, and open-source work.
  • Design Thinking: Supports design thinking processes by guiding users through problem statement, demand evidence, status quo, and target user analysis.
  • Spec Review Loop: Provides an adversarial review loop for design documents to improve quality and catch issues early.
  • Brain Calibration Write-Back: Enables tracking and calibrating predictions and decisions made during the session.
  • Handoff Sequence: Delivers a tailored closing sequence based on the user's engagement level and project status.

Quick Start

Run the office-hours Skill to start a new brainstorming session for your project.

Frequently Asked Questions about office-hours

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

FAQPage Schema
How do I structure a brainstorming session for product development?

Run an adversarial review loop for design documents to catch issues early and improve spec quality. This review mechanism challenges your design assumptions and validates technical decisions before implementation.

Can I use this for design document review and validation?

Yes, you can use it for design document review through a spec review loop that catches issues early. This adversarial review mechanism challenges your design assumptions and improves overall document quality.

What is design thinking for software engineering projects?

Design thinking for software engineering projects is a structured process guiding problem statement analysis, demand evidence, status quo evaluation, and target user assessment. It helps validate concepts and make informed product decisions.

Do I need bash and git to run strategy sessions?

You need bash, git, and gstack dependencies configured in your environment to run strategy sessions. These tools support the underlying scripts and references required for executing the brainstorming workflow.

How do I track decisions made during a design thinking session?

Track decisions during a design thinking session using the brain calibration write-back feature. This enables you to record and calibrate predictions made throughout the brainstorming process for later evaluation.

What is the best way to validate ideas for a hackathon project?

The best way to validate ideas for a hackathon project is running structured brainstorming sessions that guide you through demand evidence and target user analysis. This ensures your concepts are refined before development begins.