Agent Skills: Spec Verifier

Use when implementation or artifacts changed and evidence, alignment checking, or acceptance verification is needed.

UncategorizedID: shaowei-g/codex-skills/spec-verifier

Install this agent skill to your local

pnpm dlx add-skill https://github.com/shaowei-g/codex-skills/tree/HEAD/skills/spec-orchestrator/spec-verifier

Skill Files

Browse the full folder contents for spec-verifier.

Download Skill

Loading file tree…

skills/spec-orchestrator/spec-verifier/SKILL.md

Skill Metadata

Name
spec-verifier
Description
Use when implementation or artifacts changed and evidence, alignment checking, or acceptance verification is needed.

Spec Verifier

Use this skill when verification is the current phase for one feature.

Shared Contracts

Load this shared shortcut first:

  • ../references/shared-specialist-contract.md

Open the deeper canonical shared references only when the shortcut is insufficient for the current situation.

Purpose

Use this skill when at least one is true:

  • implementation or workflow artifacts changed
  • evidence, acceptance checks, or alignment review is needed
  • the user explicitly asks for verification or review
  • the workflow needs concrete pass/fail evidence before continuing

Read Order

  • .codex/prompts/speckit.checklist.md first
  • .codex/prompts/speckit.constitution.md if present
  • specs/<feature>/spec.md
  • specs/<feature>/plan.md if present
  • specs/<feature>/tasks.md if present
  • specs/<feature>/implementation-status.md if present
  • changed code, tests, and review artifacts needed for the assigned verification scope

Owned Outputs

  • verification evidence in the shared schema
  • explicit failures, regressions, or unverified areas
  • advisory next-step recommendation based on evidence

Phase-Specific Rejected Criteria

Return rejected if there is nothing concrete to verify or if the request is actually asking for implementation rather than verification.

Phase-Specific Blocked Criteria

Return blocked if evidence cannot be gathered because artifacts, code, test commands, fixtures, or runtime access are missing.