openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

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

100%

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

The body is a tight, actionable workflow with concrete CLI commands, an explicit stop checkpoint, and clear guardrails. It is well-organized and self-contained with no unnecessary padding.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused; brief purpose statements ('This creates a scaffolded change at...') earn their place and it avoids explaining concepts Claude already knows, matching the lean-and-efficient anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (openspec new change, openspec status, openspec instructions) with clear argument substitution guidance.	3 / 3
Workflow Clarity	A clearly numbered 1-6 sequence with an explicit STOP checkpoint and validation guardrails (invalid name, existing change); the operation is non-destructive so no feedback-loop cap applies.	3 / 3
Progressive Disclosure	Self-contained skill with well-organized sections (Input, Steps, Output, Guardrails) and no need for external references, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	12 / 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.

The description clearly answers both what the skill does and when to use it, with a distinct niche and explicit trigger guidance. It is slightly held back by listing a single core action and somewhat narrow/technical trigger terms.

Suggestions

Add one or two more concrete actions (e.g., 'scaffold a change, inspect artifact status, and fetch the first artifact template') to lift specificity from 2 to 3.

Broaden trigger terms with common phrasings users would say (e.g., 'scaffold a change', 'start an OpenSpec proposal') and downplay jargon like 'experimental artifact workflow'.

Dimension	Reasoning	Score
Specificity	Names the domain and core action ('Start a new OpenSpec change using the experimental artifact workflow') but does not enumerate multiple specific concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action level above.	2 / 3
Completeness	Explicitly states what it does ('Start a new OpenSpec change...') and when to use it via a clear 'Use when the user wants to create a new feature, fix, or modification' trigger clause.	3 / 3
Trigger Term Quality	Includes natural triggers like 'create a new feature, fix, or modification' but coverage is narrow and 'experimental artifact workflow' leans technical, so it stops short of broad natural-term coverage.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (OpenSpec change creation) with distinctive triggers, making it unlikely to fire for unrelated skills.	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-new-change/SKILL.md
Commit: 9eaff79

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