officeHours

To turn brainstorming into spec docs, this Skill channels speculative conversations into structured planning, applying EARS classification to produce product, engineering, design, and TASKS documents with explicit team mandates.

Generating multi-team planning docs from a feature idea involves validating existing bootstrap assets and prism-mcp context, then persisting a timestamped bundle of product, engineering, design, and task breakdowns to the repo's plans directory.

Yes, this spec planning workflow validates adoption of existing bootstrap assets, planning docs, and prism-mcp context before generating and persisting the four deliverable documents to ensure proper contextual grounding.

Yes, you can output separate domain-owned documents. The Skill generates product, engineering, design, and TASKS docs that capture agreed goals, EARS requirements, design direction, and coordination responsibilities for each team.

EARS requirements classification works by guiding the brainstorming session through problem discovery and contextual grounding, framing ideas rigorously in shared language so teams leave with structured, spec-driven mandates.

Brainstorming yields vague specs when lacking structured framing. This Skill solves that by channeling speculative officeHours conversations into a spec-driven discussion with explicit EARS requirements and domain-owned task breakdowns.