CtrlK
BlogDocsLog inGet started
Tessl Logo

042-planning-openspec

Use when creating or updating OpenSpec change artifacts from an issue, implementation plan, approved design, ADRs, existing OpenSpec artifacts, or a valid combination. The workflow assesses whether the scope is one change or multiple changes, records sources and derivation direction, and prevents silent synchronization. This should trigger for requests such as Create an OpenSpec change from an issue; Convert a plan into OpenSpec; Update an existing OpenSpec change; Split broad requirements into reviewable OpenSpec changes. Part of Plinth Toolkit

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured interactive skill with concrete commands, a sequenced workflow including validation checkpoints, and clean single-level progressive disclosure. Its main weakness is moderate redundancy across the 'What is covered', 'When to use', and 'Constraints' sections relative to the Workflow.

Suggestions

Collapse the 'What is covered in this Skill?' bullet list, since its items are already represented in the Constraints and Workflow sections, to remove the main source of redundancy.

Trim 'When to use this skill' to only trigger phrasings not already present in the frontmatter description, or remove it and rely on the description's triggers to avoid duplication.

Consolidate the MUST/MUST NOT 'Constraints' list so each constraint maps to a specific Workflow step, reducing overlap between the constraints and the step descriptions.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explaining of what OpenSpec or ADRs are), but the 'What is covered in this Skill?' list, 'When to use this skill', and parts of 'Constraints' restate content already conveyed by the Workflow steps, so it could be tightened.

2 / 3

Actionability

Provides concrete executable commands ('openspec --version', 'openspec init', 'openspec validate --all') and specific artifact names (proposal, design, specification deltas, tasks.md), giving copy-paste-ready guidance.

3 / 3

Workflow Clarity

Six clearly sequenced steps with an explicit validation checkpoint in step 6 ('Run openspec validate --all', archive only after validation and approval) and explicit user-decision handling for conflicts in step 5.

3 / 3

Progressive Disclosure

The body is a concise overview with a single clearly signaled one-level-deep reference to references/042-planning-openspec.md, which exists as a real bundle file, so content is appropriately split and easy to navigate.

3 / 3

Total

11

/

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 clearly states capabilities and explicit trigger conditions with natural user phrasings and a well-defined OpenSpec niche. It answers both what the skill does and when to use it without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'creating or updating OpenSpec change artifacts', 'assesses whether the scope is one change or multiple changes', 'records sources and derivation direction', and 'prevents silent synchronization', matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what ('creating or updating OpenSpec change artifacts... records sources... prevents silent synchronization') and when (the opening 'Use when...' plus 'This should trigger for requests such as...'), satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural user phrasings ('Create an OpenSpec change from an issue; Convert a plan into OpenSpec; Update an existing OpenSpec change; Split broad requirements into reviewable OpenSpec changes') alongside the domain keyword 'OpenSpec', giving good coverage of terms users would say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (OpenSpec change artifacts) with distinct triggers tied to OpenSpec-specific operations, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
jabrena/plinth
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.