openspec-continue-change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/openspec-continue-change/SKILL.md

Quality

Content

75%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.

The content is a clear, actionable workflow with concrete CLI commands and well-organized sections. Weakest in conciseness due to some repetition and in workflow validation depth, which checks file existence but not artifact correctness.

Suggestions

Consolidate the one-artifact-per-invocation rule into a single Guardrail to remove repetition across Steps, Output, and Guardrails.

Strengthen the validation checkpoint beyond file existence, e.g., re-running `openspec status --change <name> --json` after writing to confirm the artifact transitions from 'ready' to 'done' before reporting progress.

Consider moving the Common artifact patterns (spec-driven schema details) into a references file so the main SKILL.md body stays a lean overview, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without explaining OpenSpec concepts, but contains minor repetition (the one-artifact-per-invocation rule restated in Steps, Output, and Guardrails), fitting the 'efficient; minor instances that could be trimmed' anchor rather than the lean 5.	4 / 5
Actionability	It provides concrete copy-pasteable CLI commands (`openspec list --json`, `openspec status --change ... --json`, `openspec instructions ... --json`) and documents the JSON fields to parse, with minor gaps in how exactly to fill the template, matching the 'mostly executable, minor gaps' anchor.	4 / 5
Workflow Clarity	The four-step sequence is clear with a validation checkpoint ("Verify the artifact file exists after writing before marking progress") and control flow for each status branch, but validation is limited to file-existence rather than content correctness, fitting the 'clear sequence with most checkpoints, minor validation gaps' anchor.	4 / 5
Progressive Disclosure	As a self-contained single file with no bundle files and well-organized sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails), it is well structured; it scores 4 rather than 5 because the artifact-pattern reference material is inlined rather than split out, and the file exceeds the 50-line simple-skill threshold.	4 / 5
	Total	16 / 20 Passed

Description

82%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.

The description is well-formed in third person with explicit what/when structure and a distinct OpenSpec niche. Its main limitation is specificity, as it names only one concrete action rather than enumerating the artifact types it can create.

Dimension	Reasoning	Score
Specificity	The description names the OpenSpec domain and one concrete action ("creating the next artifact") but does not enumerate the broader set of artifact types, so it matches the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multi-action 4 or 5.	3 / 5
Completeness	It explicitly answers both 'what' ("Continue working on an OpenSpec change by creating the next artifact") and 'when' ("Use when the user wants to progress their change, create the next artifact, or continue their workflow") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It surfaces natural phrases users would say ("progress their change", "create the next artifact", "continue their workflow") with good coverage, though it leans on 'OpenSpec' jargon and omits a few casual synonyms, fitting the 'good keyword coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The OpenSpec-specific niche and explicit triggers make it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 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: dwmkerr/openspec-flow
Path: .claude/skills/openspec-continue-change/SKILL.md
Commit: e670a56

Reviewed: 4 days 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.