Tessl • The management layer for AI agent skills

SkillPublic

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

Quality

Content

88%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 content is a strong, execution-ready workflow: concrete CLI commands with parsed JSON fields, explicit validation checkpoints, and recovery paths for unclear input or existing changes. Its only real weakness is mild redundancy around the context/rules constraint guidance, and it appropriately needs no bundle files since all artifact structure comes from the openspec CLI itself.

Dimension	Reasoning	Score
Conciseness	The body is lean procedural instruction with executable commands throughout, but the 'context and rules are constraints, not file content' guidance is stated twice (in step 4a and again under Artifact Creation Guidelines) and a few bolded emphasis lines could be trimmed, matching the efficient-with-minor-trimmable-instances anchor.	4 / 5
Actionability	Every step is backed by copy-paste-ready CLI commands ('openspec new change', 'openspec status --change "<name>" --json', 'openspec instructions <artifact-id> --change "<name>" --json'), the returned JSON fields are enumerated, and the tools to use (AskUserQuestion, TodoWrite) are named explicitly, fully covering the common path.	5 / 5
Workflow Clarity	The sequence is explicit with dependency-ordered artifact creation, a re-run of 'openspec status' after each artifact as a validation checkpoint, a concrete stop condition (all applyRequires artifacts done), file-existence verification before proceeding, and clarification/error-recovery loops (ask the user on unclear context, handle an already-existing change), matching the top anchor.	5 / 5
Progressive Disclosure	Sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails) are clearly headed and the body is easy to navigate with no unnecessary external references; it scores just below the top anchor only because the ~93-line body keeps everything inline, which is defensible since artifact templates are supplied dynamically by the CLI.	4 / 5
	Total	18 / 20 Passed

Description

62%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 well-formed with an explicit 'Use when...' clause and a clear niche, but it stays at a summary level: it never names the concrete artifacts involved (e.g., proposal, design, tasks) and offers only one trigger phrasing, limiting specificity and trigger coverage. It is distinct within the OpenSpec ecosystem but likely overlaps with sibling OpenSpec workflow skills.

Suggestions

Name the concrete artifacts the skill produces (e.g., 'proposal, design, and tasks') in the description to raise specificity and set user expectations.

Add one or two more natural trigger phrases or synonyms users would say, such as 'spec out a change', 'scaffold an OpenSpec change', or 'generate all change artifacts at once'.

Sharpen the distinction from step-through OpenSpec skills by stating the fast-forward tradeoff explicitly (e.g., 'instead of stepping through each artifact one by one') so the right skill triggers.

Dimension	Reasoning	Score
Specificity	The description names the domain ('OpenSpec artifact creation') and one concrete action ('create all artifacts needed for implementation') but does not enumerate which artifacts are produced, matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It has a clear 'what' and an explicit 'Use when...' clause ('Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually'), but the trigger is a single condition rather than the multiple concrete trigger phrases of the top anchor, so it sits between anchors 4 and 5, closer to 4.	4 / 5
Trigger Term Quality	Relevant keywords like 'OpenSpec', 'artifacts', and 'implementation' are present, but common natural variations a user might say ('spec', 'proposal', 'tasks', 'scaffold a change') are missing, matching the some-keywords-but-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	'OpenSpec' is a clear niche with distinct triggers, but the skill's own naming convention (openspec-ff-change) implies closely related sibling skills such as a step-through artifact flow, creating minor overlap risk, which matches the mostly-distinct anchor.	4 / 5
	Total	14 / 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-ff-change/SKILL.md
Revision: a1b1216

Reviewed: 1 month ago

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.

openspec-ff-change

Table of Contents

Is this your skill?