openspec-ff-change

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Quality

79%

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-ff-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, mostly executable workflow with concrete commands and clear sequencing including verification checkpoints. It is slightly held back by some redundant restatements and an implicit rather than explicit validate-retry feedback loop.

Suggestions

Make the validation feedback loop explicit: after writing an artifact, re-run `openspec instructions`/status and fix until status is `done` before proceeding.

Trim the duplicated "context and rules are constraints" reminders into a single guardrail to reduce token overhead.

Add one short filled-in artifact example (e.g., a minimal tasks artifact) so the template guidance is concrete rather than abstract.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and minimal preamble, though the repeated "IMPORTANT" reminders and restated "Artifact Creation Guidelines" slightly restate points already made in the steps, keeping it just below fully lean.	4 / 5
Actionability	Concrete executable commands (openspec new, status --json, instructions) and clear field mappings are given throughout; minor gaps such as not showing how to parse the dependency status or a filled template example keep it from being fully copy-paste ready.	4 / 5
Workflow Clarity	A clear numbered sequence with explicit checkpoints (re-run status, verify applyRequires done, verify file exists after writing) is present, but the validate-then-proceed loop is implicit rather than a hard feedback loop, so it sits below the top anchor.	4 / 5
Progressive Disclosure	Content is well organized into Input/Steps/Output/Guidelines/Guardrails sections with no external bundle files needed; it is a self-contained overview with minor inlining of guideline material that could be separate, placing it just below the ideal.	4 / 5
	Total	16 / 20 Passed

Description

83%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 clearly states both what the skill does and when to use it, with a natural trigger phrase. It is slightly generic in its action vocabulary and could add concrete terms (e.g., "OpenSpec change", "openspec/changes") to improve specificity and distinctiveness.

Suggestions

Add concrete action verbs and terms the user would name, e.g. "scaffold an OpenSpec change and generate all artifacts (tasks, specs) in one pass".

Include a distinguishing keyword like "openspec change" or "/opsx" to reduce overlap with generic scaffolding skills.

Mention the output artifact types explicitly so the what-portion lists multiple specific actions rather than one generalized one.

Dimension	Reasoning	Score
Specificity	"quickly create all artifacts needed for implementation" names the concrete outcome (artifact creation) but the action list is essentially one generalized activity rather than multiple specific actions, placing it just above the score-3 anchor.	4 / 5
Completeness	Explicitly answers both what ("Fast-forward through OpenSpec artifact creation... create all artifacts needed for implementation") and when ("Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually"), matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ("quickly create all artifacts", "without stepping through each one individually"), but lacks synonyms or the underlying file/command vocabulary users might name, so it sits just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The OpenSpec "fast-forward artifact creation" niche is fairly distinct, but the phrasing could overlap with other scaffolding/code-gen skills and lacks a hard distinguishing trigger, leaving it just below the clear-niche anchor.	4 / 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: fengshao1227/ccg-workflow
Path: .agents/skills/openspec-ff-change/SKILL.md
Commit: cc8cc34

Reviewed: 1 day 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.