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

88%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 well-structured, highly actionable body with concrete commands, explicit confirm/validate checkpoints, and clear guardrails. The main improvement area is tightening the verbose nested tasks.md rules.

Suggestions

Move the detailed tasks.md requirement-coverage and file-less-task rules into a short reference table or a referenced file to reduce inline bulk in Step 5.

The Guardrails section repeats constraints already stated inline in the Steps; consider consolidating to remove redundancy and save tokens.

Add a one-line note that no bundle files are used, or split the longer operational rules into references/ so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence, but the nested tasks.md rules (requirement-coverage, file-less-task tags) and some restated guardrails add length that could be trimmed slightly without loss.	4 / 5
Actionability	Provides copy-paste-ready commands with exact flags and JSON field names ('openspec status --change "<name>" --json', 'artifactPaths.<id>.existingOutputPaths') and concrete examples covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced 6-step workflow with explicit validation/confirm checkpoints ('Write only after the user confirms', 'If the user rejects a revision, do not write it') and feedback loops for error recovery on a write operation.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Store selection, Input, Steps, Output, Guardrails) with no nested external references, though the longer tasks.md subsection is inlined rather than split out.	4 / 5
	Total	18 / 20 Passed

Description

87%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 clearly states what the skill does and when to use it with concrete natural-language triggers and an explicit no-code boundary. Minor room for synonyms/alternate trigger phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain (OpenSpec change planning artifacts) and several concrete actions — 'revising its existing planning artifacts', 'keeping them coherent with one another', 'reconcile its artifacts after an edit' — with only minor coverage gaps, fitting just above the 3-anchor.	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') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides natural trigger phrases users would say ('revise a change's plan', 'fold new decisions into it', 'reconcile its artifacts after an edit') but lacks synonyms or alternate phrasings, so it sits at good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to OpenSpec change-plan revision with an explicit boundary ('Never edits code') and distinct triggers, minimizing conflict with sibling OpenSpec skills like propose/apply/archive.	5 / 5
	Total	18 / 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: behindthedash/worktrail
Path: skills/openspec-update-change/SKILL.md
Commit: ca98247

Reviewed: ~3 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.