office-hours

Coordinate guided design-thinking sessions for new features in a codebase.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and structure productive, time-bound design discussions for new features within an active codebase, using a guided office-hours process to surface decisions, tradeoffs, and team alignment.

Core Features & Use Cases

  • Guided wedge-mode brainstorming: six forcing questions to determine if a feature should ship tomorrow.
  • Deep-mode exploration: 2-3 design shapes with tradeoffs for a decided feature.
  • Codebase-informed reasoning: scans relevant files and surface decisions already made in the project.
  • Intent-aware coordination: checks active intents to avoid duplicate work and coordinate across agents.

Quick Start

Invoke the office-hours command with a topic to start wedge mode, or add --deep for design-options.

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 design brainstorming session for new features in an existing codebase?

Structure a design brainstorming session by applying guided wedge-mode forcing questions or deep-mode exploration to surface codebase decisions, generate design options, and provide clear tradeoff recommendations for new features.

What is wedge mode for feature design and when should I use it?

Wedge mode is a design-thinking process using six forcing questions to determine if a feature should ship immediately. Use wedge mode to quickly validate whether a proposed feature idea is worth pursuing before committing deeper resources.

How do I evaluate design tradeoffs for a decided feature within a live project?

Evaluate design tradeoffs for a decided feature using deep-mode exploration, which scans your active codebase to surface existing decisions and generates two to three design shapes with detailed tradeoff analysis.

Can I generate multiple design options that align with my current codebase architecture?

Yes, you can generate design options that align with your codebase. The session scans relevant project files to inform reasoning, ensuring the two to three proposed design shapes reflect architectural decisions already made.

How does intent synchronization prevent duplicate work during feature design sessions?

Intent synchronization prevents duplicate work by checking active intents across agents before generating design options. This coordination ensures multiple sessions do not explore the same feature decisions concurrently.

What are the limitations of using guided design sessions for codebase feature planning?

Limitations include relying on accurate codebase scanning to surface relevant decisions and requiring active intent coordination to avoid duplication. Sessions focus on generating design options and tradeoffs rather than writing implementation code.