CtrlK
BlogDocsLog inGet started
Tessl Logo

create-plan

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body is well-sequenced with strong validation feedback loops and concrete commands, but it undermines its own progressive disclosure by inlining a template that exists as a separate reference file, leaving the example reference unused, and pointing to a validation script that is not bundled.

Suggestions

Replace the inline plan structure template with a link to references/plan-template.md, and add a pointer to references/example-plan.md as a worked example, so SKILL.md stays a lean overview.

Either bundle the validation script under scripts/ (and reference it) or drop the 'included validation script' claim and the hardcoded .forge/skills/create-plan/validate-plan.sh path, since no scripts directory ships with the skill.

Consolidate the overlapping directives in 'Critical Requirements' and 'Boundaries' (e.g., 'NEVER write code', 'ALWAYS validate') to remove redundancy and tighten token use.

DimensionReasoningScore

Conciseness

Mostly efficient and directive without explaining concepts Claude already knows, but the 'Critical Requirements' and 'Boundaries' sections repeat directives stated elsewhere (e.g., 'NEVER write code', 'ALWAYS validate') and the inline plan template duplicates references/plan-template.md, so it could be tightened.

2 / 3

Actionability

Provides concrete executable guidance — the validation command path './.forge/skills/create-plan/validate-plan.sh plans/...', a specific naming convention with a worked example (plans/2025-11-24-add-auth-v1.md), and a complete plan structure template, which is copy-paste ready for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 4-step Planning Process sequence with an explicit mandatory validation step and a feedback loop ('Fix any errors or warnings and re-validate until the plan passes all checks'), plus a Critical Requirements checklist — matching the score-3 anchor.

3 / 3

Progressive Disclosure

The bundle ships references/plan-template.md and references/example-plan.md, but the body never links them — it inlines the template instead and references a validation script at .forge/skills/create-plan/validate-plan.sh that is not present in the bundle (no scripts/ directory), so references are present but not signaled and content that should be separate is inline.

2 / 3

Total

10

/

12

Passed

Description

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

A strong description: concrete capabilities, explicit trigger guidance, and a clear planning-only boundary distinguishing it from implementation skills. Voice stays in acceptable third-person/imperative form with no first/second-person penalty.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches' and validation 'using the included validation script', matching the score-3 anchor of several concrete actions.

3 / 3

Completeness

Clearly answers both what ('Generate detailed implementation plans... validated using the included validation script') and when ('Use when users need thorough analysis and structured planning... or when they explicitly ask for a plan, roadmap, or strategy') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would actually say — 'plan, roadmap, or strategy', 'structured planning', 'breaking down complex features' — in an explicit 'Use when...' trigger clause, giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

A clear planning-only niche with the explicit boundary 'Strictly planning-focused with no code modifications', making it unlikely to trigger for implementation or other skills.

3 / 3

Total

12

/

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
tailcallhq/forgecode
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.