officeHours

What problem does it solve?

Too often brainstorming yields vague ideas or sprawling specs that no one owns; this Skill channels those sessions into a structured, spec-driven discussion with explicit EARS requirements so each team leaves with a clear mandate and deliverable.

Core Features & Use Cases

• Structured brainstorming: Guides the session through problem discovery, contextual grounding, and EARS classification so the team frames ideas rigorously and in shared language.
• Domain-owned outputs: Generates product, engineering, design, and TASKS documents that capture the agreed goals, requirements, approach, and coordination responsibilities for each team.
• Planning readiness: Leverages existing bootstrap assets, planning docs, and prism-mcp context before creating a timestamped plan bundle, keeping GitHub issues as the single source of truth.

Quick Start

Run /officeHours [feature or problem] to kick off the spec session and output the product, engineering, design, and TASKS docs.