← ClaudeAtlas

spec-first-brainstorminglisted

Problem frame: Use when a chosen change needs behavior delta, scope, constraints, or readiness. Own frame/next owner; Skip ideation, design, and tasks.
Dankosik/go-service-template-rest · ★ 7 · API & Backend · score 76
Install: claude install-skill Dankosik/go-service-template-rest
# Spec First Brainstorming Consume the requester-meaning authority selected by [Phase Selection](../../../docs/spec-first-workflow.md#phase-selection). Return to [Intake](../../../docs/spec-first-workflow/phases/intake.md) when that input is missing or leaves requester meaning unresolved. Build the frame by reconstructing every behavior delta, scope boundary, constraint, assumption, risk, owner, and proof expectation from that authority, current contracts, and affected user/operator surfaces. Decide every technical unit yourself from current evidence and keep only a question that survives [Decision Ownership](../../../AGENTS.md#decision-ownership), then disposition each unit as represented, preserved, decided default, open decision, external input, or blocker so Specification need not guess meaning. 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.