agentleFS
charliehzmcharliehzm/medharness/.claude/skills/openspec-verify-change/SKILL.md

openspec-verify-change

Skill85 starsChanged 6 months agoApache-2.0View on GitHub

Use this skill at Step 7 of the v2 SOP to verify that all tasks in the active OpenSpec change are implemented and align with their specs. Cross-checks tasks.md checkboxes against actual code presence, runs per-spec acceptance criteria as smoke tests where possible, and surfaces unimplemented artifacts. Verify is a HARD GATE: failure routes back to Step 6 (openspec-apply-change) until clear. Chinese trigger examples: "OpenSpec verify", "Step 7", "核验变更", "检查未实现工件". Do NOT use to judge code quality (that's Step 8 review), do NOT use to verify compliance (that's Step 10). Success = every task checked, every spec has evidence, unimplemented-artifact list is empty.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openspec-ff-change, openspec-onboard and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    openspec-ff-change

    Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

    Also in 65 projects that use this

  • MicrosoftSkill

    openspec-onboard

    Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

    Also in 61 projects that use this

  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • goernSkill

    release-openspec

    Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    openspec-update-change

    Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

    Also in 21 projects that use this

  • SentrySkill

    code-simplifier

    Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

    Also in 3 projects that use this

  • +1 more from microsoft
  • +2 more from goern

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run acceptance criteria smoke tests for each spec.

    line 44
  2. Distinctive:

    If any failure → return to Step 6, fix, re-run.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSpec Verify Change

The "did we actually build what we said" gate.

What it checks (NOT code quality)

CheckPass criterion
Tasks checkbox parityevery [x] task has a referenced code change in git
Spec evidenceevery spec id appears in commit messages / file headers / test names
Acceptance criteria smokeper-spec acceptance criteria runnable on stage-mock data, smoke green
File scope disciplineno task exceeded 2 files
Compliance touchpointsevery L3/L4-touching task's PR mentions phi-desensitize use

Workflow

  1. Parse tasks.md / tasks/*.md → list of completed tasks + intended files.
  2. Diff against git log / current workspace → identify gaps.
  3. For each gap, mark as one of: missing-file / missing-test / missing-checkbox / scope-overflow.
  4. Run acceptance criteria smoke tests for each spec.
  5. Emit VERIFY_REPORT.md with passes / failures / actions.

Hard gate

If any failure → return to Step 6, fix, re-run. Do not pass to Step 8.

Common failure modes

  1. Checkbox theater — task marked done without code. Mitigation: parity check.
  2. Hidden Steve work — task touched 4 files. Mitigation: scope discipline check.
  3. Spec without test hook — acceptance criteria not executable. Mitigation: hand back to openspec-continue-change to refine.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.