agentleFS
trivoallantrivoallan/ontrack/.claude/skills/openspec-verify-change/SKILL.md

openspec-verify-change

Skill1 starsChanged 2 days agoApache-2.0View on GitHub

Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".

81 other projects use a version of this, 76 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use draft-openspec-docs, release-openspec and 6 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.
  • 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

  • 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

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 3 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 3 projects that use this

  • OpenAISkill

    executing-plans

    Use when you have a written implementation plan to execute in a separate session with review checkpoints

    Also in 3 projects that use this

  • +2 more from goern

The file

Show its rules and text

We split this skill into the rules it gives an agent

39 rules. 33 are common, 2 are distinctive, and 4 are very specific to this project.

  • 33

    Common

    Most of the 78 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Verify that an implementation matches the change artifacts (specs, tasks, design).

    line 13
  2. Distinctive:

    If a name is provided, use it.

    line 34
  3. Very specific:

    If ambiguous, run openspec list --json to get available changes and ask the user to select one

    line 37
  4. Distinctive:

    When prompting, show changes that have implementation tasks (tasks artifact exists).

    line 39
  5. Very specific:

    Always announce: "Using change: <name>" and how to override (e.g., /opsx:verify <other>).

    line 43
  6. Common:

    Create a report structure with three dimensions:

    line 64
  7. Very specific:

    If contextFiles.tasks exists, read every file path in it

    line 74
  8. Common:

    If incomplete tasks exist:

    line 79
  9. Common:

    Add CRITICAL issue for each incomplete task

    line 80
  10. Very specific:

    If delta specs exist in contextFiles.specs:

    line 84
  11. Common:

    Search codebase for keywords related to the requirement

    line 87
  12. Common:

    If requirements appear unimplemented:

    line 89
  13. Common:

    Add CRITICAL issue: "Requirement not found: <requirement name>"

    line 90
  14. Common:

    Search codebase for implementation evidence

    line 97
  15. Common:

    If found, note file paths and line ranges

    line 98
  16. Common:

    Add WARNING: "Implementation may diverge from spec: <details>"

    line 101
  17. Common:

    Check if conditions are handled in code

    line 106
  18. Common:

    Check if tests exist covering the scenario

    line 107
  19. Common:

    If scenario appears uncovered:

    line 108
  20. Common:

    Add WARNING: "Scenario not covered: <scenario name>"

    line 109
  21. Common:

    Verify implementation follows those decisions

    line 117
  22. Common:

    Add WARNING: "Design decision not followed: <decision>"

    line 119
  23. Common:

    If no design.md: Skip design adherence check, note "No design.md to verify against"

    line 121
  24. Common:

    Check file naming, directory structure, coding style

    line 125
  25. Common:

    If significant deviations found:

    line 126
  26. Common:

    Add SUGGESTION: "Code pattern deviation: <details>"

    line 127
  27. Common:

    If CRITICAL issues: "X critical issue(s) found.

    line 162
  28. Common:

    If only warnings: "No critical issues.

    line 163
  29. Common:

    If all clear: "All checks passed.

    line 164
  30. Common:

    Correctness: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty

    line 169
  31. Common:

    Coherence: Look for glaring inconsistencies, don't nitpick style

    line 170
  32. Common:

    False Positives: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL

    line 171
  33. Common:

    Actionability: Every issue must have a specific recommendation with file/line references where applicable

    line 172
  34. Common:

    If only tasks.md exists: verify task completion only, skip spec/design checks

    line 176
  35. Common:

    If tasks + specs exist: verify completeness and correctness, skip design

    line 177
  36. Common:

    If full artifacts: verify all three dimensions

    line 178
  37. Common:

    Always note which checks were skipped and why

    line 179
  38. Common:

    Use clear markdown with:

    line 183
  39. Common:

    No vague suggestions like "consider reviewing"

    line 188

“Common” is measured: kept by at least 6 in 10 of the 78 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

Verify that an implementation matches the change artifacts (specs, tasks, design).

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Project check: These steps expect a project that already uses OpenSpec. Before the first step that writes anything (new change, archive, sync specs, or authoring an artifact file), confirm the project has a root: run openspec list --json (with --store <id> when a store is selected, since the store is then the root) and read root. A root object means the project is set up. "root": null means it is not - there is no openspec/ directory here, and a write such as openspec new change would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.

One "root": null is not about setup: when a status error message starts with Declared in or Invalid store declaration in and names this project's openspec/config.yaml (or config.yml), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the store: line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's message and fix.

Otherwise, with no root, what happens next depends on how this workflow was reached:

  • Auto-selected: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
  • Explicit OpenSpec request: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (openspec init), target a store they already have (--store <id>), or continue without OpenSpec for this request. Wait for their answer.

In both branches, never create the root as a side effect: do not run openspec init until the user asks for it, do not hand-create openspec/ files, and do not let a command create it.

Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

  1. Select the change

    If a name is provided, use it. Otherwise:

    • Infer from conversation context if the user mentioned a change
    • Auto-select if only one active change exists
    • If ambiguous, run openspec list --json to get available changes and ask the user to select one

    When prompting, show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with incomplete tasks as "(In Progress)".

    Always announce: "Using change: <name>" and how to override (e.g., /opsx:verify <other>).

  2. Check status to understand the schema
    openspec status --change "<name>" --json
    Parse the JSON to understand:
    • schemaName: The workflow being used (e.g., "spec-driven")
    • planningHome, changeRoot, artifactPaths, and actionContext: path and scope context
    • Which artifacts exist for this change
  3. Get planning context and load artifacts

    openspec instructions apply --change "<name>" --json

    This returns the change directory and contextFiles (artifact ID -> array of concrete file paths). Read all available artifacts from contextFiles.

  4. Initialize verification report structure

    Create a report structure with three dimensions:

    • Completeness: Track tasks and spec coverage
    • Correctness: Track requirement implementation and scenario coverage
    • Coherence: Track design adherence and pattern consistency

    Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.

  5. Verify Completeness

    Task Completion:

    • If contextFiles.tasks exists, read every file path in it
    • Parse checkboxes: complete means the box holds only x/X, ignoring spacing (- [ x] is complete); every other marker is incomplete (- [ ], - [], and unfamiliar ones such as - [~] or - [-])
    • Count complete vs total tasks
    • If incomplete tasks exist:
      • Add CRITICAL issue for each incomplete task
      • Recommendation: "Complete task: <description>" or "Mark as done if already implemented"

    Spec Coverage:

    • If delta specs exist in contextFiles.specs:
      • Extract all requirements (marked with "### Requirement:")
      • For each requirement:
        • Search codebase for keywords related to the requirement
        • Assess if implementation likely exists
      • If requirements appear unimplemented:
        • Add CRITICAL issue: "Requirement not found: <requirement name>"
        • Recommendation: "Implement requirement X: <description>"
  6. Verify Correctness

    Requirement Implementation Mapping:

    • For each requirement from delta specs:
      • Search codebase for implementation evidence
      • If found, note file paths and line ranges
      • Assess if implementation matches requirement intent
      • If divergence detected:
        • Add WARNING: "Implementation may diverge from spec: <details>"
        • Recommendation: "Review <file>:<lines> against requirement X"

    Scenario Coverage:

    • For each scenario in delta specs (marked with "#### Scenario:"):
      • Check if conditions are handled in code
      • Check if tests exist covering the scenario
      • If scenario appears uncovered:
        • Add WARNING: "Scenario not covered: <scenario name>"
        • Recommendation: "Add test or implementation for scenario: <description>"
  7. Verify Coherence

    Design Adherence:

    • If contextFiles.design exists:
      • Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
      • Verify implementation follows those decisions
      • If contradiction detected:
        • Add WARNING: "Design decision not followed: <decision>"
        • Recommendation: "Update implementation or revise design.md to match reality"
    • If no design.md: Skip design adherence check, note "No design.md to verify against"

    Code Pattern Consistency:

    • Review new code for consistency with project patterns
    • Check file naming, directory structure, coding style
    • If significant deviations found:
      • Add SUGGESTION: "Code pattern deviation: <details>"
      • Recommendation: "Consider following project pattern: <example>"
  8. Generate Verification Report

    Summary Scorecard:

    ## Verification Report: <change-name>
    
    ### Summary
    | Dimension    | Status           |
    |--------------|------------------|
    | Completeness | X/Y tasks, N reqs|
    | Correctness  | M/N reqs covered |
    | Coherence    | Followed/Issues  |

    Issues by Priority:

    1. CRITICAL (Must fix before archive):
      • Incomplete tasks
      • Missing requirement implementations
      • Each with specific, actionable recommendation
    2. WARNING (Should fix):
      • Spec/design divergences
      • Missing scenario coverage
      • Each with specific recommendation
    3. SUGGESTION (Nice to fix):
      • Pattern inconsistencies
      • Minor improvements
      • Each with specific recommendation

    Final Assessment:

    • If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
    • If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
    • If all clear: "All checks passed. Ready for archive."

Verification Heuristics

  • Completeness: Focus on objective checklist items (checkboxes, requirements list)
  • Correctness: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
  • Coherence: Look for glaring inconsistencies, don't nitpick style
  • False Positives: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
  • Actionability: Every issue must have a specific recommendation with file/line references where applicable

Graceful Degradation

  • If only tasks.md exists: verify task completion only, skip spec/design checks
  • If tasks + specs exist: verify completeness and correctness, skip design
  • If full artifacts: verify all three dimensions
  • Always note which checks were skipped and why

Output Format

Use clear markdown with:

  • Table for summary scorecard
  • Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
  • Code references in format: file.ts:123
  • Specific, actionable recommendations
  • No vague suggestions like "consider reviewing"

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.