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. Also use when the user says "openspec ff" or "opsx ff".

Quality

77%

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 ./skills/openspec-ff-change/SKILL.md

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 highly actionable and workflow-safe: exact commands, named JSON fields, validation after every write, and careful handling of uninitialized-project and store edge cases. The main cost is token efficiency — guidance is repeated across Step 4, the Artifact Creation Guidelines, and Guardrails sections, which could be consolidated.

Suggestions

Consolidate the duplicated guidance: 're-read dependencies from disk', the context/rules exclusion, and dependency-reading appear in Step 4a, Artifact Creation Guidelines, and Guardrails — state each once.

Break up or externalize the two dense opening prose blocks (Store selection, Project check) into a short summary in SKILL.md with detail in a reference file.

Merge the adjacent bullets in step 4b that both cover skipped/skip_specs artifacts into a single rule to reduce repeated conditions.

Dimension	Reasoning	Score
Conciseness	Most content earns its place (CLI semantics like status being file-existence-only are non-obvious), but there is real duplication: 're-read dependencies from disk' appears in step 4a, the Guardrails, and the Artifact Creation Guidelines; the context/rules exclusion rule is stated twice; and the skipped-artifact handling is covered in adjacent bullets. This places it at 'mostly efficient but could be tightened' rather than the 4 anchor.	3 / 5
Actionability	Fully executable throughout: copy-paste commands (`openspec new change "<name>"`, `openspec status --change "<name>" --json`, `openspec instructions <artifact-id> --change "<name>" --json`) with the exact JSON fields to parse (`applyRequires`, `requires`, `resolvedOutputPath`, `planningHome`) and explicit branch handling for each outcome.	5 / 5
Workflow Clarity	Clear numbered sequence with explicit validation checkpoints and feedback loops: re-run `status --json` after each artifact, verify the artifact exists at `resolvedOutputPath`, explicit stop conditions, and error-path handling (`"root": null`, non-zero exits, store-declaration errors). The batch-operation cap does not apply since verification steps are present.	5 / 5
Progressive Disclosure	A self-contained single file (no bundle files exist to reference) with clear sections and no nested references. Good structure, but the dense opening prose blocks (store selection, project check) run long inline and would benefit from being split or pulled into a reference, so it does not fully meet the 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

73%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.

A strong description with an explicit 'Use when' clause and distinct literal command triggers, making it easy to select correctly. Its main weakness is specificity: the capability is described at a high level ('create all artifacts') without naming what those artifacts are or what the fast-forward path concretely delivers.

Suggestions

Enumerate the concrete capabilities, e.g. 'creates the proposal, specs, design, and tasks artifacts for a change in one pass' to lift specificity above the 1-2-action level.

Add natural trigger variations users are likely to say, such as 'scaffold', 'generate', or 'skip the wizard', alongside the existing 'openspec ff' / 'opsx ff' aliases.

Briefly state the output the user gets (a complete, implementation-ready change directory) so the 'what' is concrete rather than implied.

Dimension	Reasoning	Score
Specificity	The description names the domain ('OpenSpec artifact creation') and one concrete capability ('create all artifacts needed for implementation'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not enumerate several specific actions, so it is not the level-4 anchor.	3 / 5
Completeness	Both 'what' ('Fast-forward through OpenSpec artifact creation') and 'when' ('Use when the user wants to... Also use when the user says...') are explicitly present with concrete trigger phrases. Not a 5 because the 'what' is a single high-level clause rather than a concrete enumeration of the capabilities delivered.	4 / 5
Trigger Term Quality	Good natural keyword coverage including literal command aliases ('openspec ff', 'opsx ff') and a plain-language trigger ('quickly create all artifacts... without stepping through each one individually'). A few natural synonyms users might say ('scaffold', 'generate artifacts') are missing, so it falls short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (OpenSpec artifact creation) with distinct literal trigger commands ('openspec ff', 'opsx ff') that no other skill would claim, giving minimal conflict risk.	5 / 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: Fission-AI/OpenSpec
Path: skills/openspec-ff-change/SKILL.md
Commit: 2500d6d

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.