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.
82
74%
Does it follow best practices?
Impact
90%
1.60xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/0-planning/SKILL.mdEvaluation results
94%
30%Webhook Delivery System — Implementation Plan
Technical plan directory structure and no-code constraint
Correct root directory
0%
100%
plan.md present
0%
100%
Phased files present
0%
100%
No runnable code
30%
50%
Options with trade-offs
83%
100%
Pseudocode or code sketch
100%
100%
Junior-developer detail
100%
100%
YAGNI adherence
87%
87%
Security addressed
100%
100%
Performance addressed
100%
100%
Self-contained context
88%
100%
90%
45%Annual Developer Hackathon — Project Plan
Non-technical project plan format and required sections
Correct file location
0%
50%
YAML frontmatter present
0%
100%
plan_id field
0%
100%
status field value
0%
100%
category field value
0%
100%
phase field value
0%
100%
priority field value
0%
100%
Vision & Objectives section
50%
100%
Scope & Deliverables section
33%
100%
Action Steps with owners
62%
100%
Action Steps with deadlines
87%
50%
Resources Required section
80%
100%
Timeline & Milestones section
100%
100%
Risks with contingencies
100%
100%
SMART success metrics
80%
90%
created field present
0%
100%
87%
27%User Audit Logging — Implementation Plan
Pre-planning check and technical quality standards
Existing plan referenced
100%
100%
Consistent codebase patterns
100%
100%
Security: tamper resistance or access control
100%
100%
Performance: sync vs async logging
40%
70%
Maintainability addressed
50%
70%
Options with trade-offs
20%
100%
Correct plan directory structure
0%
100%
No implemented code
0%
40%
YAGNI: no out-of-scope features
87%
87%
Phased task breakdown
100%
100%
- Repository
- majiayu000/claude-skill-registry-data
- Commit
a331d7c
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.