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.
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill planning90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 90%
↑ 1.60xAgent success when using this skill
Validation for skill structure
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels in specificity, trigger term coverage, and completeness with an explicit 'Use when' clause. The main weakness is its intentionally universal scope, which while comprehensive, could create selection conflicts with more specialized planning skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions including 'feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment' and action verbs like 'plan, architect, design, evaluate, breakdown, structure projects'. | 3 / 3 |
Completeness | Clearly answers both what (capabilities and actions listed) AND when with explicit 'Use when:' clause specifying triggers like 'planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs' - these are terms users naturally use when seeking planning help. | 3 / 3 |
Distinctiveness Conflict Risk | While comprehensive, the 'Universal planning' scope is intentionally broad and could overlap with domain-specific skills (e.g., a dedicated software architecture skill or a business strategy skill). The breadth is a feature but creates potential conflict with more specialized planning skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured planning skill that efficiently covers both technical and non-technical domains. Its strengths are excellent organization, clear workflow sequencing, and appropriate use of progressive disclosure. The main weakness is that actionable guidance is deferred to reference files, making the main skill somewhat abstract without concrete examples of what a good plan looks like.
Suggestions
Add a brief concrete example of a completed plan section (e.g., a sample 'Vision & Objectives' with SMART goals) to make the guidance more actionable without relying entirely on external templates
Include a minimal inline example of the technical plan output (plan.md structure) so users can understand the expected format without navigating to reference files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables and bullet points effectively. It assumes Claude's competence with concepts like YAGNI, KISS, DRY, and SMART goals without explaining them. Every section earns its place. | 3 / 3 |
Actionability | Provides clear structure and workflow steps, but lacks concrete executable examples. The output structure and frontmatter templates are helpful, but the actual planning guidance relies heavily on external reference files rather than providing copy-paste ready content. | 2 / 3 |
Workflow Clarity | Clear sequenced workflows for both technical and project planning modes. The pre-planning protocol includes explicit validation (check for existing plan, ask user). Skip conditions are clearly stated for workflow steps. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references. Technical workflow steps link to specific reference files, and project templates are clearly organized. Navigation is intuitive. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.