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

92%

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

85%

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

A well-organized, actionable process skill with a clear sequenced workflow, explicit validation checkpoints, and clean one-level progressive disclosure. The main weakness is mild redundancy between the overview/trigger sections and the description and workflow.

Suggestions

Remove the 'When to use this skill' list (it duplicates the trigger phrases already in the description) or replace it with a one-line pointer to the description.

Collapse the 'What is covered in this Skill?' bullets into the Workflow intro to eliminate overlap with the step detail.

Verify the reference file's xi:include of assets/java-design-plan-template.md — no assets/ directory exists in the bundle, so that nested template reference is currently broken.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the 'What is covered in this Skill?' bullets and 'When to use this skill' list duplicate content already conveyed by the description and the Workflow section, so it could be tightened.	2 / 3
Actionability	Gives concrete, actionable guidance for an instruction-only skill: exact command ('Run date'), exact file to read ('references/041-planning-plan-mode.md'), an explicit source-classification scheme, and a precise conflict-resolution and approval procedure.	3 / 3
Workflow Clarity	A clearly sequenced six-step workflow (0–5) with explicit validation checkpoints — 'wait for approval before writing' and 'Do not propagate conflicting changes until the user makes an explicit decision' — providing the required feedback loops.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single, well-signaled one-level-deep reference (references/041-planning-plan-mode.md) that exists in the bundle, with content appropriately split rather than inlined.	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 description: concrete capabilities, natural trigger phrasing, explicit what-and-when guidance, and a distinct niche, all in third-person voice. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating or refining a structured Java implementation plan' from a named set of source types (issue summaries, approved designs, ADRs, OpenSpec changes, existing plans) — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (creating/refining a structured Java implementation plan from specific sources) and when via a 'Use when...' clause plus enumerated trigger requests, satisfying the top anchor.	3 / 3
Trigger Term Quality	Includes natural phrases users would say — 'Create a plan from an issue', 'Create a plan from OpenSpec', 'Design an implementation plan', 'Refine an existing plan' — giving good coverage of likely request wording.	3 / 3
Distinctiveness Conflict Risk	The Java implementation-planning niche with concern-specific source authority and distinct enumerated triggers is clearly distinguishable and 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/041-planning-plan-mode/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.