plan-writing

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Install with Tessl CLI

npx tessl i github:lchenrique/politron-ide --skill plan-writing

What are skills?

Quality

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/plan-writing/SKILL.md

SKILL.md

Review

Evals

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.

This description has good structure with an explicit 'Use when' clause that clearly communicates both purpose and triggers. However, it could be more specific about concrete actions and include more natural trigger terms users would actually say. The description is functional but could be strengthened to better differentiate from general development or project management skills.

Suggestions

Add more specific concrete actions like 'create step-by-step task lists', 'identify dependencies and blockers', 'define acceptance criteria'

Include additional natural trigger terms users might say: 'plan', 'break down', 'organize', 'steps', 'todo list', 'project planning'

Dimension	Reasoning	Score
Specificity	Names the domain (task planning) and some actions (breakdowns, dependencies, verification criteria), but lacks concrete specific actions like 'create task lists', 'identify blockers', or 'generate checklists'.	2 / 3
Completeness	Clearly answers both what (structured task planning with breakdowns, dependencies, verification criteria) and when (implementing features, refactoring, multi-step work) with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes some relevant terms ('implementing features', 'refactoring', 'multi-step work') but misses common variations users might say like 'plan', 'break down', 'organize tasks', 'project planning', 'todo', or 'steps'.	2 / 3
Distinctiveness Conflict Risk	While 'task planning' is somewhat specific, terms like 'implementing features' and 'refactoring' could overlap with coding/development skills. The planning focus helps but isn't strongly distinctive.	2 / 3
	Total	9 / 12 Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid planning skill with excellent actionability through concrete examples and clear wrong/right comparisons. The structure is well-organized and easy to follow. However, it could be more concise by reducing repetitive emphasis and consolidating some of the principle tables, and would benefit from explicit validation steps for the planning workflow itself.

Suggestions

Consolidate the five principles into a more compact format - the wrong/right tables are helpful but repetitive in structure

Add a validation checkpoint for reviewing/revising plans before execution (e.g., 'Review: Does each task have a clear verification step?')

Dimension	Reasoning	Score
Conciseness	The skill has some redundancy and could be tightened. The repeated emphasis on 'NOT templates' and multiple tables showing wrong vs right patterns add bulk. The principles are useful but could be more condensed.	2 / 3
Actionability	Provides concrete, specific examples throughout - exact commands like 'npx create-next-app', file paths like '/api/auth/[...nextauth].ts', and verification steps like 'curl localhost:3000/api/users returns 200'. The wrong/right tables give clear actionable guidance.	3 / 3
Workflow Clarity	The plan structure is clear and the principles are well-sequenced, but lacks explicit validation checkpoints for the planning process itself. States 'Verification is always LAST' but doesn't provide a feedback loop for when plans need revision.	2 / 3
Progressive Disclosure	Well-organized with clear sections (Overview, Principles, Structure, Best Practices, When to Use). Content is appropriately structured for a single skill file with no need for external references. Easy to navigate and scan.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.