CtrlK
BlogDocsLog inGet started
Tessl Logo

planning-workflow

Complete planning workflow orchestrating architecture planning, task breakdown, and progress tracking setup. Sequential workflow from requirements analysis through structure design and task breakdown to implementation tracking. Use when planning complex skills, setting up comprehensive project plans, or preparing for systematic skill development with full planning artifacts.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/planning-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

A clearly sequenced orchestration skill with concrete outputs and good sectioning, weakened by heavy repetition of the same three steps across multiple sections. Collapsing the redundant restatements would materially improve token efficiency.

Suggestions

Collapse the 'Workflow (3 steps)' overview list and the 'Quick Reference' table into a single table; keep the detailed per-step section as the only prose expansion to remove the triple restatement.

Drop the closing line 'planning-workflow provides complete planning from requirements to ready-to-executable task list.' since it restates the opening Overview verbatim.

Trim the repeated 'Time' estimates that appear in both the detailed steps and the Quick Reference table to a single location.

DimensionReasoningScore

Conciseness

The same three steps are restated three times — as the 'Workflow (3 steps)' overview, the detailed 'Planning Workflow' section, and the 'Quick Reference' table — and the closing line repeats the opening overview, making it noticeably padded.

2 / 5

Actionability

Names the skill to run for each step, its sub-steps, and the concrete output file ('skill-architecture-plan.md', 'task-breakdown.md', 'todo-list.md'); actionable for an orchestration skill though it omits explicit invocation syntax.

4 / 5

Workflow Clarity

Clear three-step sequence with explicit handoffs ('using plan from Step 1'); the skill is non-destructive so the validation cap does not apply, though no checkpoints are present at all.

4 / 5

Progressive Disclosure

Self-contained ~60-line skill with well-organized sections and no bundle files needed; minor organization gap from the Overview/Quick Reference duplication rather than a structure problem.

4 / 5

Total

14

/

20

Passed

Description

83%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.

A strong description that clearly states both capability and trigger conditions with concrete actions and natural keywords. Minor improvement possible by tightening redundant action phrasing and swapping jargon terms for plainer synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('orchestrating architecture planning, task breakdown, and progress tracking setup'; 'from requirements analysis through structure design and task breakdown to implementation tracking'), with minor redundancy between 'architecture planning' and 'structure design'.

4 / 5

Completeness

Explicitly answers both what ('Complete planning workflow orchestrating architecture planning, task breakdown, and progress tracking setup') and when ('Use when planning complex skills, setting up comprehensive project plans, or preparing for systematic skill development').

5 / 5

Trigger Term Quality

Good coverage of natural terms ('planning complex skills', 'comprehensive project plans', 'progress tracking'), though 'systematic skill development' and 'full planning artifacts' lean technical and a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct planning-workflow niche, but the named component skills (planning-architect, task-development, todo-management) create minor overlap risk for closely related planning requests.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.