planning

Universal planning for technical and non-technical projects. Domains: software implementation, business, personal, creative, academic, events. Capabilities: feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment. Actions: plan, architect, design, evaluate, breakdown, structure projects. Keywords: implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs. Use when: planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements.

1.60x

Quality

81%

Does it follow best practices?

Impact

90%

1.60x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

71%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-organized, actionable instruction-only skill with clear workflows and templates. Its primary defect is progressive disclosure: it points to eight reference files that do not exist in the bundle, breaking the navigation it promises.

Suggestions

Ship the referenced bundle files under references/ (research-phase.md, codebase-understanding.md, solution-design.md, plan-organization.md, output-standards.md, business-plan-template.md, personal-goal-template.md, generic-plan-template.md), or remove the dangling references and inline the essential content.

De-duplicate the reference list: the files appear both inline in the Technical Implementation workflow and again in the References section — keep one canonical, clearly signaled listing.

Add a brief inline validation/checklist step to the technical workflow (e.g., verify the plan covers scope, trade-offs, and task breakdown before finalizing) so the sequence has an explicit feedback loop rather than only pointers to references.

Dimension	Reasoning	Score
Conciseness	Efficient, table/list-driven body with no over-explanation of concepts Claude already knows; docked from 5 because the reference files are listed both inline in the workflow and again in the References section, a minor redundancy.	4 / 5
Actionability	Provides concrete guidance — exact plan directory layout, a full frontmatter template with field enums, required section list, and an executable pre-planning command ('test -f docs/plan.md && cat docs/plan.md'); not 5 because the technical workflow steps are pointers to references with no inline detail.	4 / 5
Workflow Clarity	Clear sequencing with skip conditions, a pre-planning validation checkpoint ('If exists: Ask user to continue or create new'), and a Quality Standards checklist; not 5 because the technical workflow steps themselves lack inline validation/feedback loops. Planning is not destructive, so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Structure and reference signaling are good (dedicated References section, one-level-deep pointers), but all eight referenced files (research-phase.md, codebase-understanding.md, solution-design.md, plan-organization.md, output-standards.md, business-plan-template.md, personal-goal-template.md, generic-plan-template.md) are absent from the bundle, so the disclosed detail is non-functional; not 4 because missing bundle files are more than a minor gap.	3 / 5
	Total	15 / 20 Passed

Description

92%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 comprehensive and well-structured, explicitly covering what the skill does and when to use it with strong trigger-term coverage. Its main weakness is breadth: 'universal planning' across six domains creates real overlap risk with more specialized skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete planning actions across domains — 'feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment' — matching the comprehensive-coverage anchor; not the 4 anchor because coverage is broad rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what ('Universal planning for technical and non-technical projects' plus capabilities/actions) and when ('Use when: planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements') with concrete triggers.	5 / 5
Trigger Term Quality	Keywords span natural user phrases with synonyms — 'implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs'; matches comprehensive synonym coverage rather than the 4 anchor's 'a few natural terms missing'.	5 / 5
Distinctiveness Conflict Risk	'Universal planning' spanning software, business, personal, creative, academic, and events is broad, and triggers like 'designing architecture' and 'implementation plan' overlap with dedicated coding/architecture skills; not 2 because a planning-only niche (plans/docs, not execution) gives some distinction, not 4 because overlap risk remains material.	3 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 16 missing	Warning

	Total	15 / 16 Passed

Repository: majiayu000/claude-skill-registry
Path: skills/data/0-planning/SKILL.md
Commit: 04324c6

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