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

Low

Low-risk findings worth noting

Quality

Content

85%

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, actionable overview that defers detail to one real reference and sequences its workflow with explicit approval gates. Its main weakness is redundancy across the intro, coverage list, constraints, and workflow.

Suggestions

Collapse the redundancy around OpenSpec independence: state the 'plan-only, OpenSpec not required' rule once in the Workflow and reference it from Constraints rather than repeating it in the intro, coverage list, and step 5.

Trim the Constraints section so each MUST/MUST NOT adds information not already stated in the Workflow steps, or fold the constraints into their corresponding workflow steps.

Merge the 'What is covered in this Skill?' bullet list with the 'When to use this skill' list to avoid overlapping restatements of scope and triggers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no concept explanations), but repeats itself: the OpenSpec-not-required point appears in the intro, "What is covered", Constraints, and Workflow step 5, and the Constraints section largely restates the Workflow steps.	2 / 3
Actionability	Gives concrete executable guidance (run `date`, read the named reference file, classify sources by concern with explicit categories, confirm named derivation fields), with specific MUST/MUST NOT rules — actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Steps 0–5 are clearly sequenced with explicit validation/approval checkpoints ("wait for approval before writing", "Do not propagate conflicting changes until the user makes an explicit decision"), matching the top anchor.	3 / 3
Progressive Disclosure	The body is an overview with a single clearly-signaled one-level-deep reference link to references/041-planning-plan-mode.md (a real bundle file), 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.

The description is third-person, concise, and clearly states both capability and trigger conditions with concrete natural-language examples. It distinguishes the skill well via its artifact-driven Java planning niche.

Dimension	Reasoning	Score
Specificity	Names concrete actions ("creating or refining a structured Java implementation plan") and enumerates specific 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 named sources) and when (an explicit "Use when..." clause plus enumerated trigger requests), satisfying the top anchor.	3 / 3
Trigger Term Quality	Includes natural trigger 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 common variations.	3 / 3
Distinctiveness Conflict Risk	The Java implementation-planning niche framed around authoritative source artifacts has distinct triggers and is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	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/plinth
Path: skills/041-planning-plan-mode/SKILL.md
Commit: a8e5189

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.