041-planning-plan-mode

Use when creating or refining a structured Java implementation plan from trusted issue summaries, approved designs, ADRs, OpenSpec changes, existing plans, or a valid combination. The plan records its source artifacts and derivation direction and can remain the execution artifact without requiring OpenSpec. This should trigger for requests such as Create a plan from an issue; Create a plan from OpenSpec; Design an implementation plan; Refine an existing plan. Part of Plinth Toolkit

Quality

81%

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

Quality

Content

78%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 well-structured, lean overview with a clear sequenced workflow, explicit approval/validation gates, and proper one-level-deep progressive disclosure to a verified reference. The main weaknesses are mild redundancy between the 'What is covered', Constraints, and 'When to use' sections and slightly high-level workflow step bodies.

Suggestions

Consolidate the 'What is covered in this Skill?' list with the Constraints/Workflow sections or trim it to remove overlap with the description's trigger phrases.

Tighten workflow step bodies (e.g. step 4 'Generate the implementation plan') by listing the concrete sub-structure or a one-line template pointer instead of restating the section list.

Add an explicit validate->fix->retry feedback loop for plan validation (e.g. on summary approval failure) to push workflow_clarity from a gate-based 4 toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullets and crisp MUST/MUST NOT constraints with no concept over-explanation, but the 'What is covered in this Skill?' list overlaps the Constraints and Workflow sections and 'When to use' repeats the description's triggers, so minor trimming is possible without a full 5.	4 / 5
Actionability	Concrete executable guidance is present ('Run `date` before planning', 'Read references/041-planning-plan-mode.md', 'Ask one or two focused questions', 'wait for approval before writing'), but the bulk of plan-structure detail is deferred to the reference and several workflow steps remain high-level, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly sequenced 0–5 workflow with explicit validation/approval checkpoints ('wait for explicit user resolution before propagating a conflict', 'Validate the summary and wait for approval before writing', 'do not maintain silent two-way synchronization'); not a 5 because some step bodies are terse and the validation steps are gates rather than full validate->fix->retry loops.	4 / 5
Progressive Disclosure	SKILL.md is a well-organized overview with clearly signaled one-level-deep navigation to a real reference file ('For detailed guidance, examples, and constraints, see references/041-planning-plan-mode.md'), and the referenced file exists, giving easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

83%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 strong: it states the what and when explicitly with concrete trigger phrases, uses correct third-person voice, and carves a clear Java-planning niche. Minor gaps in action specificity and trigger synonym coverage keep two dimensions at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('structured Java implementation plan') and several concrete actions (create/refine plan, 'records its source artifacts and derivation direction', 'can remain the execution artifact'), but the actions are planning-process verbs rather than fully comprehensive concrete operations, so it sits above the 3 anchor but below 5.	4 / 5
Completeness	Explicitly answers both what ('creating or refining a structured Java implementation plan... records its source artifacts and derivation direction') and when ('Use when creating or refining...', 'This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases via 'This should trigger for requests such as Create a plan from an issue; Create a plan from OpenSpec; Design an implementation plan; Refine an existing plan', giving good keyword coverage; a few natural synonyms are missing so it is not a full 5.	4 / 5
Distinctiveness Conflict Risk	The Java + source-artifact-recording + OpenSpec-optional framing carves a clear niche with distinct triggers, but 'planning' broadly still risks minor overlap with other planning/refinement skills, placing it just below a clean 5.	4 / 5
	Total	17 / 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: jabrena/plinth
Path: skills/041-planning-plan-mode/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.