plan
Scope validated ideas into work items, decompose projects into parallel workstreams and epics, sequence milestones, map dependencies, and pressure-test the plan with a pre-mortem.
63
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./develop/skills/plan/SKILL.mdQuality
Discovery
67%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 excels at listing specific, concrete project planning actions and occupies a clear niche, making it distinctive. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill from a large pool. The trigger terms lean toward project management jargon and miss common natural language phrases users might employ.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to plan a project, create a roadmap, break down work, or organize tasks into sprints or milestones.'
Include more natural user-facing trigger terms such as 'project planning', 'roadmap', 'task breakdown', 'sprint planning', 'project kickoff', or 'backlog creation' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'scope validated ideas into work items', 'decompose projects into parallel workstreams and epics', 'sequence milestones', 'map dependencies', and 'pressure-test the plan with a pre-mortem'. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | The 'what' is well-covered with specific actions, but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. The 'when' is only implied by the actions themselves, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Contains relevant domain terms like 'work items', 'epics', 'milestones', 'dependencies', 'workstreams', and 'pre-mortem', but misses common natural language variations users might say such as 'project planning', 'roadmap', 'task breakdown', 'sprint planning', or 'project management'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of project decomposition, workstream parallelization, milestone sequencing, dependency mapping, and pre-mortem analysis creates a very distinct niche focused on project scoping and planning. This is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 strong planning skill with excellent structure, clear workflows, and highly actionable guidance. The four-move framework (Scope, Decompose, Sequence, Pre-mortem) provides a clean mental model with concrete steps and validation checkpoints. The main weakness is moderate verbosity — some sections (particularly Story mapping from discovery and the stance description) could be tightened to save tokens without losing clarity.
Suggestions
Tighten the 'Your Stance' section — the two-lens concept could be conveyed in 2 sentences instead of a full paragraph.
The 'Story mapping from discovery' pattern is the longest section and could be condensed by ~30%, e.g., combining steps 1-2 and trimming explanatory asides like 'This is the spine of the mapping.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections are verbose — e.g., the 'Your Stance' section's philosophical framing and the 'Story mapping from discovery' pattern is quite lengthy. Several bullet points could be tightened without losing meaning. | 2 / 3 |
Actionability | The skill provides highly concrete, specific guidance: exact file paths (docs/discovery/ideas/<slug>.md), explicit artifact schemas to consult, named fields to set (from_discovery), clear processes with numbered steps, and specific anti-patterns. While there's no executable code, this is an instruction-only planning skill where the guidance is fully actionable. | 3 / 3 |
Workflow Clarity | The four moves are clearly sequenced with explicit inputs, outputs, and validation checkpoints (e.g., 'M1 without a demo-able outcome isn't a milestone,' 'when discovery is incomplete, story mapping isn't ready'). The story mapping and spec→tasks processes have clear numbered steps with decision points and feedback loops. Failure modes section serves as a validation checklist. | 3 / 3 |
Progressive Disclosure | Excellent structure: the main file provides a clear overview of four moves with enough detail to act, then points to one-level-deep references (references/scope.md, references/decompose.md, etc.) and per-type artifact guides (project.md, epic.md, etc.). Navigation is well-signaled with a dedicated 'Detailed Guidance' section and inline links throughout. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- audenaert/etak
- Commit
632c389
- 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.