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

76%

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 ./.agents/skills/openspec-continue-change/SKILL.md

Quality

Content

77%

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

A well-structured, actionable workflow with concrete CLI commands, clear sequencing, and a verification checkpoint. The main gaps are minor redundancy in the guardrails and inline schema-pattern detail that could be split into a reference file.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with executable commands and no concept-padding, but the Guardrails section restates rules already given in step 3 (e.g., 'Create ONE artifact per invocation', 'context and rules are constraints') and includes a filler line ('This shouldn't happen with a valid schema'), so it could be tightened.	2 / 3
Actionability	Provides fully executable `openspec list/status/instructions` commands and parses concrete JSON fields (schemaName, artifacts, template, outputPath), making guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear numbered 1–4 sequence with an explicit verification checkpoint ('Verify the artifact file exists after writing before marking progress') and per-invocation STOP points; the operation is single-artifact rather than batch/destructive, so no validation cap applies.	3 / 3
Progressive Disclosure	Sections are well-organized and runtime detail is delegated to `openspec instructions`, but with no bundle files and over 50 lines the inline spec-driven schema patterns (proposal/specs/design/tasks) are content that could live in a separate reference.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 clear, well-triggered description with explicit 'Use when' guidance and a distinct OpenSpec niche. It is slightly held back by naming only one action and by trigger terms that are narrow and partly jargon-bound.

Dimension	Reasoning	Score
Specificity	Names the domain (OpenSpec change) and one concrete action ('creating the next artifact'), but does not enumerate multiple distinct actions, so it falls short of the level-3 'multiple specific concrete actions' anchor.	2 / 3
Completeness	Clearly answers what it does ('Continue working on an OpenSpec change by creating the next artifact') and when to use it via an explicit 'Use when...' clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Includes relevant natural phrases ('progress their change', 'create the next artifact', 'continue their workflow'), but coverage is narrow and leans on skill-specific jargon ('artifact') without common variations a user might say.	2 / 3
Distinctiveness Conflict Risk	The 'OpenSpec change' niche is specific and unlikely to trigger for unrelated skills, satisfying the clear-niche/distinct-triggers anchor.	3 / 3
	Total	10 / 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: fengshao1227/ccg-workflow
Path: .agents/skills/openspec-continue-change/SKILL.md
Commit: 9eaff79

Reviewed: about 14 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.