CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

project-planning

tessl i github:jezweb/claude-skills --skill project-planning
github.com/jezweb/claude-skills

Generate structured planning docs for web projects with context-safe phases, verification criteria, and exit conditions. Creates IMPLEMENTATION_PHASES.md plus conditional docs. Use when: starting new projects, adding major features, or breaking large work into manageable phases.

Review Score

66%

Validation Score

12/16

Implementation Score

55%

Activation Score

67%

SKILL.md
Review
Evals

Generated

Validation

Total

12/16

Score

Passed
CriteriaScore

skill_md_line_count

SKILL.md is long (1123 lines); consider splitting into references/ and linking

metadata_version

'metadata' field is not a dictionary

license_field

'license' field is missing

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Implementation

Suggestions 4

Score

55%

Overall Assessment

This skill provides comprehensive, actionable guidance for project planning with excellent workflow clarity and concrete templates. However, it severely violates token efficiency by embedding ~600+ lines of template boilerplate that should be in separate referenced files. The content is well-structured but the monolithic approach makes it impractical for context window management.

Suggestions

  • Extract all template structures (DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, UI_COMPONENTS.md, CRITICAL_WORKFLOWS.md, INSTALLATION_COMMANDS.md, ENV_VARIABLES.md, SESSION.md templates) into separate referenced files like `templates/DATABASE_SCHEMA_TEMPLATE.md`
  • Reduce the main SKILL.md to ~150-200 lines covering: workflow overview, phase types summary, validation rules, and links to template files
  • Move the 'Default Stack Knowledge' section to a separate STACK_DEFAULTS.md file that can be referenced when needed
  • Consolidate the 'Phase Type' definitions into a compact table rather than verbose subsections with repeated structure
DimensionScoreReasoning

Conciseness

1/3

Extremely verbose at ~800+ lines with extensive template boilerplate that Claude doesn't need spelled out. Explains obvious concepts (what a PDF is equivalent: what phases are, what verification means) and includes full template structures that could be referenced externally.

Actionability

3/3

Highly actionable with concrete templates, specific file structures, executable bash commands, and copy-paste ready examples. The phase templates, mermaid diagrams, and installation commands are all directly usable.

Workflow Clarity

3/3

Excellent workflow structure with clear 6-step recommended workflow, explicit validation rules (≤8 files, ≤4 hours), verification requirements per phase type, and auto-split logic for oversized phases. Includes quality checklist and common mistakes section.

Progressive Disclosure

1/3

Monolithic wall of text with all templates inline rather than referenced. The 8+ full template structures (DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, UI_COMPONENTS.md, etc.) should be in separate referenced files, not embedded in the main skill.

Activation

Suggestions 2

Score

67%

Overall Assessment

This description has good structure with an explicit 'Use when' clause and mentions specific outputs, earning strong completeness marks. However, it uses somewhat technical jargon ('context-safe phases', 'exit conditions') that may not match natural user language, and the trigger scenarios are broad enough to potentially conflict with other project-related skills.

Suggestions

  • Add more natural trigger terms users would say, such as 'plan', 'roadmap', 'break down tasks', 'project phases', or 'implementation plan'
  • Replace technical terms like 'context-safe phases' and 'exit conditions' with user-friendly language describing the concrete benefits or outputs
DimensionScoreReasoning

Specificity

2/3

Names the domain (web project planning) and some actions (generate planning docs, creates IMPLEMENTATION_PHASES.md), but 'context-safe phases', 'verification criteria', and 'exit conditions' are somewhat technical/abstract rather than concrete user-facing actions.

Completeness

3/3

Clearly answers both what (generate structured planning docs with phases, verification criteria, exit conditions, creates specific files) and when (explicit 'Use when:' clause with three trigger scenarios).

Trigger Term Quality

2/3

Includes some natural terms like 'new projects', 'major features', 'phases', but misses common variations users might say like 'plan', 'roadmap', 'breakdown', 'task list', 'milestones', or 'project structure'.

Distinctiveness Conflict Risk

2/3

Specific to web project planning docs and mentions unique outputs (IMPLEMENTATION_PHASES.md), but 'starting new projects' and 'adding major features' could overlap with general project scaffolding or code generation skills.