042-planning-openspec

Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an issue; Convert a plan into OpenSpec; Update an OpenSpec change; Split broad requirements into reviewable changes. Part of Plinth Toolkit

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

70%

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

A well-structured, validation-aware planning workflow with clean progressive disclosure, weakened mainly by repetition of the /create-spec issue-mode rules and a lack of inline artifact examples. Tightening the duplication and adding a minimal proposal/tasks template would raise it.

Suggestions

State the /create-spec issue-mode completeness rules once (in Workflow Step 1) and have the Constraints MUST bullets reference that detail instead of repeating it verbatim, to reduce token redundancy.

Add a minimal inline example of a proposal.md/spec delta and the single tasks.md checklist so artifact authoring is actionable without opening the reference.

Merge the four /create-spec-related MUST bullets in Constraints into one consolidated rule to further cut repetition.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational, but the /create-spec issue-mode completeness rules are repeated near-verbatim across the Constraints MUST bullets and Workflow Step 1 (and again in the reference), so it could be tightened.	2 / 3
Actionability	Concrete CLI commands are present ('openspec --version', 'openspec new change <change-id>', 'openspec validate --all'), but the artifact-authoring steps give direction without inline examples or templates, leaving key details to the reference.	2 / 3
Workflow Clarity	Six clearly numbered steps with explicit validation checkpoints — the completeness stop-gate, 'openspec validate --all', and user-approval gates before multi-change maps and archiving — plus a feedback loop for conflicting sources.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with a well-signaled, one-level-deep Reference section pointing to the real references/042-planning-openspec.md; content is appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person description that explicitly pairs capability with 'Use when'/'Triggers include' guidance and concrete actions. The only minor blemish is the trailing 'Part of Plinth Toolkit' tag, which is promotional but harmless.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating or updating OpenSpec artifacts', 'assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization' — rather than vague language.	3 / 3
Completeness	Both what and when are explicit: the opening 'Use when creating or updating OpenSpec artifacts...' states purpose, and the 'Triggers include...' clause gives explicit invocation guidance.	3 / 3
Trigger Term Quality	Explicit 'Triggers include Create OpenSpec from an issue; Convert a plan into OpenSpec; Update an OpenSpec change; Split broad requirements into reviewable changes' covers natural phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The OpenSpec change-planning niche with its distinct trigger list is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: jabrena/cursor-rules-java
Path: skills/042-planning-openspec/SKILL.md
Commit: fdaf68c

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.