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

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 ./.claude/skills/openspec-new-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 body is a well-structured, actionable workflow with concrete CLI commands, clear sequencing, and a STOP checkpoint, all delivered concisely without over-explaining known concepts. Its only real weakness is slight redundancy between the inline guidance and the Guardrails section.

Suggestions

De-duplicate the Guardrails against the inline steps (e.g., the --schema and kebab-case rules appear in both) to tighten conciseness toward 5.

Add a brief validation cue after `openspec status` (e.g., 'confirm the change directory was created before proceeding') to make the checkpoint sequence fully explicit.

Pin or note where the first-artifact-id comes from with a one-line example (e.g., 'proposal' for the spec-driven schema) to remove the one dynamic gap in actionability.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding explaining concepts Claude already knows; minor redundancy between the inline steps and the Guardrails section keeps it just below 5.	4 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands (openspec new change, openspec status, openspec instructions, openspec schemas) and a named tool (AskUserQuestion), with a minor gap where the first-artifact-id is resolved dynamically from status output rather than given explicitly.	4 / 5
Workflow Clarity	A clear six-step numbered sequence with an explicit 'STOP and wait' checkpoint and name-validation guardrails; not a destructive or batch operation so the missing validate-fix-retry loop does not cap the score, but checkpoints are otherwise implicit rather than fully spelled out.	4 / 5
Progressive Disclosure	No bundle files are needed for this single-purpose skill, and the body is well-organized into clearly labeled Input, Steps, Output, and Guardrails sections; it sits just below 5 only because there is no explicit cross-file navigation to demonstrate one-level-deep referencing.	4 / 5
	Total	16 / 20 Passed

Description

78%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 concise, uses third-person voice, and clearly answers both what and when with a natural trigger clause. It is strong on completeness but only moderately specific since it describes a single action rather than a comprehensive capability set.

Suggestions

Add one or two more concrete capabilities (e.g., 'scaffolds the change directory, resolves the workflow schema, and surfaces the first artifact template') to lift specificity toward 5.

Include a few more natural trigger synonyms or the CLI name (e.g., 'openspec change', 'scaffold a change') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec change', 'experimental artifact workflow') and the core action of starting a change, but coverage is a single action rather than a comprehensive list of concrete capabilities.	3 / 5
Completeness	Clearly states what it does ('Start a new OpenSpec change using the experimental artifact workflow') and when to use it ('Use when the user wants to create a new feature, fix, or modification'), satisfying both what and when with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('create a new feature, fix, or modification', 'change') with good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The 'OpenSpec' and 'artifact workflow' niche is fairly distinct with clear triggers, though it could marginally overlap with other OpenSpec-related skills.	4 / 5
	Total	16 / 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-new-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.