← ClaudeAtlas

pre-spec-challengelisted

Pressure-test: Use when research/framing needs discriminating questions before spec/planning. Own hidden risks and next owner; Skip blank framing, ordinary review, or one approval question.
Dankosik/go-service-template-rest · ★ 7 · API & Backend · score 73
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. Resolve every branch you can from current evidence; a question reaches the user only under [Decision Ownership](../../../AGENTS.md#decision-ownership). 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.