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

87%

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

85%

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 workflow skill with clear sequencing, validation checkpoints, and good organization. The main weakness is minor redundancy between the Steps and the later Guardrails/Guidelines sections.

Suggestions

Remove the redundancy between Step 3's 'STOP after creating ONE artifact' and the Guardrails 'Create ONE artifact per invocation' by consolidating the constraint in one place.

Trim overlap between the 'Artifact Creation Guidelines' schema patterns and Step 3's instruction-field handling so each section earns its tokens.

Dimension	Reasoning	Score
Conciseness	The body avoids concept-explanation padding, but 'Guardrails' re-states 'Create ONE artifact per invocation' already covered in Step 3, and the 'Artifact Creation Guidelines' overlap with Step 3, so it could be tightened.	2 / 3
Actionability	It provides concrete, executable CLI commands (openspec list/status/instructions with --json) and enumerates the exact JSON fields to parse, making guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear numbered sequence with status-based branching, explicit STOP checkpoints, and a verification step ('Verify the artifact file exists after writing before marking progress') provides strong workflow clarity.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a self-contained, well-sectioned workflow with no nested references; per the simple-skill scoring note, well-organized sections with no need for external references score 3.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 concise, third-person description that clearly states both its purpose and explicit trigger conditions, with low conflict risk. Its only weakness is listing a single action rather than enumerating several concrete capabilities.

Suggestions

Enumerate the concrete artifact types the skill creates (e.g., proposals, specs, design docs, task lists) to raise specificity from a single action to multiple specific capabilities.

Dimension	Reasoning	Score
Specificity	Names the OpenSpec domain and a concrete action ('creating the next artifact'), but lists only a single action rather than multiple specific capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It states what the skill does and includes an explicit 'Use when the user wants to...' trigger clause, clearly answering both what and when.	3 / 3
Trigger Term Quality	Phrases like 'progress their change', 'create the next artifact', and 'continue their workflow' are natural terms a user would say, giving good trigger coverage.	3 / 3
Distinctiveness Conflict Risk	'OpenSpec change' is a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-continue-change/SKILL.md
Commit: be872c1

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