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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is lean, well-organized, and actionable with a clearly sequenced workflow and approval/conflict checkpoints. Its main weakness is bundle integrity: the core plan-generation step depends on an included template file that is not present in assets/.

Suggestions

Add the missing assets/java-design-plan-template.md referenced by the xi:include in references/041-planning-plan-mode.md, or replace the include with an inline template, so Step 4 generation is actually executable.

Reduce the light repetition of the OpenSpec-optional point across 'What is covered', 'Constraints', and the workflow to tighten token use.

Make the validation/checkpoint language in the workflow steps explicit labels (e.g. 'CHECKPOINT: wait for approval before writing') so the gating steps are unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is terse and organized with imperative MUST/MUST NOT constraints and no explanations of concepts Claude already knows; it assumes competence and every section earns its place, with only minor repetition of the OpenSpec-optional point.	3 / 3
Actionability	Gives concrete, executable guidance — 'Run `date` before planning', 'Read references/041-planning-plan-mode.md', classify sources by concern, ask focused questions, and required plan sections — appropriate for an instruction-only skill.	3 / 3
Workflow Clarity	A numbered 0–5 workflow with explicit checkpoints ('wait for approval before writing', 'wait for explicit user resolution before propagating a conflict') and conflict-gating feedback, which suits this non-destructive planning task.	3 / 3
Progressive Disclosure	The body is a clean overview pointing to a single clearly-signaled one-level reference, but the reference resolves Step 4 generation via an xi:include to assets/java-design-plan-template.md and the assets/ directory does not exist, so a referenced bundle path is broken.	2 / 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 specific, complete, and well-triggered: it names concrete planning actions, includes natural trigger phrases, and clearly answers both what and when. It carves a distinct Java-implementation-planning niche with only minor overlap risk within its own toolkit family.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'creating or refining a structured Java implementation plan', 'records its source artifacts and derivation direction', and 'can remain the execution artifact' — which matches the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (create/refine a structured Java implementation plan, record sources and derivation) and when (explicit 'Use when...' clause plus enumerated trigger examples).	3 / 3
Trigger Term Quality	Provides natural trigger phrasings 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 'structured Java implementation plan' niche with source-authority and derivation-direction framing has distinct triggers unlikely to collide with unrelated skills, though it is part of a broader toolkit family.	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
Commit: aaee915

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.