test-spec

# Test spec authoring Design proof before implementation. ## Workflow role - role_name: test-spec - stage: authoring - upstream: approved spec and review, approved plan, and applicable architecture or ADRs - downstream: test-spec-review - summary: Map settled requirements and execution intent to concrete proof before implementation. - ownership: Author test-spec content and, with exact governed authority, only its authoring evidence and matching artifact-entry transition. - must_not_claim: implementation, validation, verification, branch, PR, release, deployment, publication, or peer-review completion Portable work is isolated. Workflow-managed execution does not enlarge the `test-spec` write set. ## Quick operating guide Use this skill to create or revise a proof map from settled requirements and execution intent. Read first: the approved spec and review, plan, applicable architecture, project guidance, test conventions, and both initially required boundary references. Produce: traceable cases, coverage and command ledgers, milestone proof timing, explicit gaps, and a `test-spec-review` handoff. Stop when: required input, identity, proof, authority, resource, or output is unsafe to infer. Do not claim: implementation or downstream readiness. Next stage: required `test-spec-review` for formal governed authoring. ## Purpose and use Before implementation, create or revise proof from governing artifacts, repository guidance, test conventions, fixtures, commands, and...