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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, executable workflow with concrete CLI commands, specific JSON field references, explicit confirm-before-write checkpoints, and clear guardrails. The only mild weakness is the density of the store-selection paragraph, which could be tightened.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (references JSON fields by name without explaining JSON or OpenSpec); not a 5 because the store-selection paragraph is dense and could be trimmed slightly.	4 / 5
Actionability	Fully executable, copy-paste-ready commands (openspec status --change with --json, openspec instructions <artifact-id> --change with --json) with specific JSON field paths (artifactPaths.<id>.existingOutputPaths) covering the common cases.	5 / 5
Workflow Clarity	Clear 6-step sequence with explicit validation/confirmation checkpoints (confirm before write, reject => no write, 'If the change is already coherent, say so') and feedback loops, satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections (Store selection, Input, Steps, Output, Guardrails) with one-level-deep, clearly signaled references to sibling skills and no nested reference chains; appropriate for a self-contained skill with no bundle files.	5 / 5
	Total	19 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and gives explicit 'Use when' trigger guidance with a clear code-editing boundary. It could be slightly sharpened with more synonyms and artifact-type specificity, but it is well above average.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('revising its existing planning artifacts', 'keeping them coherent', 'fold new decisions into it', 'reconcile its artifacts') with only minor gaps in coverage; not a 5 because it does not enumerate the artifact types or revision modes comprehensively.	4 / 5
Completeness	Explicitly answers both what ('Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent') and when ('Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('revise a change's plan', 'fold new decisions into it', 'reconcile its artifacts'); not a 5 because the terminology is fairly specialized and omits common synonyms or extensions.	4 / 5
Distinctiveness Conflict Risk	Clear niche (OpenSpec change planning artifacts) sharpened by 'Never edits code'; not a 5 because it shares the openspec-change namespace with sibling skills, leaving minor overlap risk.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Fission-AI/OpenSpec
Path: skills/openspec-update-change/SKILL.md
Commit: 6926ccb

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.