CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-planning

AI DevKit · Planning phase guidance for creating and reconciling feature task plans. Use when the user wants to create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks, or run dev-lifecycle planning work.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The content is concise, actionable, and well-sequenced with explicit lint-based validation checkpoints and clear phase transitions. It is a strong, self-contained instruction skill with no padding and no unnecessary reference indirection.

DimensionReasoningScore

Conciseness

The body is lean and procedural with no concept explanations or padding — e.g. 'Run `npx ai-devkit@latest lint` before phase work' and 'Convert goals, user stories, design components... into implementation tasks' — assuming Claude's competence so every token earns its place.

3 / 3

Actionability

Provides concrete, executable commands throughout (`npx ai-devkit@latest lint`, `npx ai-devkit@latest lint --feature <name>`, resolving `.ai-devkit.json` paths.docs) with specific step-by-step guidance; absence of full code blocks is appropriate for this instruction-only skill.

3 / 3

Workflow Clarity

Clear sequenced workflows for both Create Initial Plan (1–9) and Update Planning (1–8) with an explicit validation gate ('Run lint before phase work') and a verify step ('Verify every test-plan scenario has at least one implementation task'), plus explicit phase transitions ('Next: dev-implementation').

3 / 3

Progressive Disclosure

No bundle files are present or needed; the ~43-line body is self-contained and organized into clear sections (Phase Contract, Create Initial Plan, Update Planning), which satisfies the score-3 simple-skill allowance for under-50-line skills with no external references.

3 / 3

Total

12

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 is specific and complete, clearly stating both capabilities and explicit use-when triggers. It could be strengthened by replacing internal jargon ('dev-lifecycle') and broadening natural trigger variations.

Suggestions

Replace or gloss the internal term 'dev-lifecycle' with user-facing phrasing so the trigger reads naturally to end users.

Add a few more common natural variations of the triggers (e.g. 'make a task list', 'track feature progress') to broaden coverage.

Tighten the product prefix ('AI DevKit · Planning phase guidance') so the core action-led capability is not buried behind tool branding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'creating and reconciling feature task plans', 'create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks', matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Planning phase guidance for creating and reconciling feature task plans') and when ('Use when the user wants to create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks...'), satisfying the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Includes some natural phrases a user would say ('create an implementation plan', 'update planning docs', 'capture blockers'), but leans on internal jargon like 'dev-lifecycle' and lacks the breadth of common natural variations seen in the score-3 anchor.

2 / 3

Distinctiveness Conflict Risk

Scoped to the AI DevKit planning phase with planning-specific triggers (create/update plans, capture blockers), giving it a clear niche unlikely to trigger for sibling dev-lifecycle skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.