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

80%

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

85%

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

The content is a highly actionable, well-sequenced workflow with executable commands and clear validation feedback loops. Its only weakness is mild redundancy between the step body and the closing guidelines section.

Suggestions

Remove the duplicated 'context and rules are constraints, not file content' guidance from the 'Artifact Creation Guidelines' section since it is already stated in step 4a, or consolidate it into one place to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean procedural commands, but the 'Artifact Creation Guidelines' section restates the context/rules constraint already given in step 4a and repeats dependency-reading guidance, so it could be tightened.	2 / 3
Actionability	It provides concrete, executable `openspec` commands with flags, enumerates the exact JSON fields to parse, and names specific tools (TodoWrite, AskUserQuestion), giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with validation checkpoints (re-run `openspec status --json` after each artifact, check `applyRequires` status is 'done') plus a guardrail to verify each file exists before proceeding.	3 / 3
Progressive Disclosure	The skill is a single self-contained file with well-labeled sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails) and no nested external references, which is appropriate for a tightly-coupled workflow.	3 / 3
	Total	11 / 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 is complete and distinct with an explicit 'Use when' trigger and a well-defined OpenSpec niche. It is held back only by jargon ('fast-forward') and a lack of multiple concrete, naturally-spoken action terms.

Suggestions

Replace the jargon verb 'fast-forward' with a natural user phrase and add concrete actions, e.g. 'Generate all OpenSpec artifacts (tasks, specs, deltas) in one pass. Use when the user wants to create every artifact for a change at once instead of stepping through them individually.'

Add natural trigger terms a user would actually say ('create the artifacts', 'generate specs and tasks', 'set up the change') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec artifact creation') and a main action ('create all artifacts needed for implementation') but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It explicitly states what the skill does ('Fast-forward through OpenSpec artifact creation') and when to use it via a clear 'Use when...' clause, satisfying both the what and the when with an explicit trigger.	3 / 3
Trigger Term Quality	The 'Use when' clause supplies relevant keywords ('create all artifacts', 'implementation') but 'fast-forward' is jargon users would rarely say, and common variations are missing, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Scoping to 'OpenSpec artifact creation' is a clear, narrow niche with distinct triggers that is 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-ff-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.