pre-spec-challengelisted

Pressure-test: Use when existing research or framing needs a few independent, discriminating questions before specification or planning. Own questions about hidden assumptions, ownership, failure semantics, irreversible consequences, and rollout risk, plus the next owner; Skip when framing is blank, ordinary spec review is needed, or one isolated high-impact approval question is primary.
Dankosik/go-service-template-rest · ★ 6 · API & Backend · score 75

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

# Pre Spec Challenge Pressure-test the fixed synthesis read-only by reconstructing every material assumption, owner, failure semantic, irreversible consequence, rollout decision, and next-owner claim from its evidence boundary. Use only discriminating questions and disposition each branch as an anchored concern, evidence-backed no concern, outside boundary, or proof blocked. Use [Specification](../../../docs/spec-first-workflow/phases/specification.md) and load [the reference selector](references/index.md) only when one concrete seam can change the result. Missing policy ends with a named Specification Decision handoff; otherwise return the concise challenge or evidence-backed no concern and next owner.