spec-first-brainstorminglisted

Problem frame: Use when a chosen or mostly chosen feature/refactor direction still needs an engineering-ready behavior delta, scope, constraints, assumptions, and readiness decision. Own that frame, prioritized questions, challenge routing, and next owner; Skip when raw ideation, final design decisions, or task breakdown is primary.
Dankosik/go-service-template-rest · ★ 6 · API & Backend · score 75

Install: claude install-skill Dankosik/go-service-template-rest

# Spec First Brainstorming Build the frame by reconstructing every behavior delta, scope boundary, constraint, assumption, risk, owner, and proof expectation from the chosen direction, current contracts, and affected user/operator surfaces. Ask only questions that sharpen those units, then disposition each as represented, preserved, open decision, external input, or blocker so Specification need not guess meaning. Use [the workflow router](../../../docs/spec-first-workflow.md) and load [the reference selector](references/index.md) only when one concrete pressure can change the frame, challenge routing, or readiness. Complete with the frame, readiness and challenge-routing decisions, and the named next owner.