CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-ff-change/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced workflow with concrete commands, explicit validation checkpoints, and feedback loops. Its main weakness is redundancy across the Steps, Guidelines, and Guardrails sections, which hurts conciseness and organization.

Suggestions

Collapse the Artifact Creation Guidelines and Guardrails sections into the relevant Steps (or a single short checklist) to remove restated constraints like 'read dependencies', 'use template', and 'verify file exists'.

Move the long store-selection paragraph into a short pointer with the exception rule stated once, since it interrupts the main workflow before the input/steps.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding about concepts Claude already knows, but the Steps, Artifact Creation Guidelines, and Guardrails sections noticeably restate the same constraints (read dependencies, use template, context/rules are constraints, verify file exists), which could be tightened.

3 / 5

Actionability

It provides copy-paste-ready `openspec` commands, names the exact JSON fields to parse, and gives concrete decision rules for walking requires edges and handling skipped artifacts, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation (verify each artifact file exists before proceeding, re-run `openspec status` after each artifact), feedback loops (creating one can unblock others; re-check), and a todo-list checklist; the batch-operation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

The content is well-organized into labeled sections with no nested references and no external files needed, but at over 50 lines the Guidelines and Guardrails sections overlap with the Steps, leaving a minor organization gap short of the clean-split anchor.

4 / 5

Total

17

/

20

Passed

Description

75%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 answers both what the skill does and when to use it, with a distinctive OpenSpec niche and explicit trigger phrasing. It is weakest on action breadth and trigger-term variation, naming essentially one action and few synonyms.

Suggestions

Add one or two more concrete actions (e.g., 'scaffold the change, generate specs, design, and tasks in one pass') to lift specificity beyond a single action.

Include a couple of natural synonyms a user might say (e.g., 'scaffold', 'bootstrap', 'generate all specs') alongside 'create all artifacts' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ('OpenSpec artifact creation') and one concrete action ('fast-forward' / 'quickly create all artifacts'), but does not list several specific actions, so it stops at the '1-2 concrete actions' anchor rather than the comprehensive-coverage anchor above.

3 / 5

Completeness

It gives a clear 'what' ('Fast-forward through OpenSpec artifact creation') and an explicit, concrete 'when' ('Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually'), matching the anchor that requires both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'quickly create all artifacts' and 'implementation' appear, but the triggers are narrow and tied to a niche tool with no synonyms or common variations, fitting the 'some relevant keywords but missing variations' anchor rather than the good-coverage anchor above.

3 / 5

Distinctiveness Conflict Risk

The OpenSpec-specific niche plus the distinctive 'fast-forward / without stepping through each one' framing give it a clear niche with minimal overlap risk, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Fission-AI/OpenSpec
Reviewed

Table of Contents

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.