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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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 clear, well-sequenced planning workflow with a strong validation feedback loop; main weaknesses are a referenced validation script that is absent from the bundle and mild duplication between the inline template and the plan-template reference.

Suggestions

Ship the referenced validation script (or correct its path) so the MANDATORY validate-plan.sh step is actually runnable, and consider moving it under scripts/ to match the bundle convention.

Replace the fully inlined plan structure template with a pointer to references/plan-template.md to reduce duplication and keep the body as an overview.

Trim redundancy between Critical Requirements, Boundaries, and When to Use so each rule appears once.

Dimension	Reasoning	Score
Conciseness	Sections are well-organized and mostly lean, but Critical Requirements and Boundaries restate guidance from When to Use/Planning Process, and 'describe in natural language, not code' is repeated, indicating minor over-explanation.	4 / 5
Actionability	Concrete file-naming convention, a full inline plan template, and a specific validation command make guidance mostly executable, but the mandated validation script path (./.forge/skills/create-plan/validate-plan.sh) is not present in the bundle, leaving the key step un-runnable as written.	4 / 5
Workflow Clarity	The 4-step Assess -> Create -> Validate -> Structure flow has a MANDATORY validation checkpoint with an explicit fix-and-re-validate feedback loop, matching the top anchor for sequenced validation.	5 / 5
Progressive Disclosure	References/example-plan.md and references/plan-template.md are real and one level deep, but the body inlines a full plan template that largely duplicates plan-template.md, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

92%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, specific description that clearly states what the skill produces and when to use it, with concrete trigger phrases and a clear disambiguating boundary against implementation work.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete artifacts (objectives, checkbox tasks, verification criteria, risk assessments, alternative approaches), matching the 'comprehensive coverage' anchor.	5 / 5
Completeness	Clearly answers both 'what' (generates strategic Markdown plans with listed components) and 'when' via an explicit 'Use when...' clause with concrete triggers, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'plan, roadmap, or strategy' and 'structured planning' are present, but a few common synonyms (e.g. 'blueprint', 'breakdown') are missing, landing between good and comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'Strictly planning-focused with no code modifications' qualifier and distinct planning triggers carve a clear niche with minimal overlap against implementation skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tailcallhq/forgecode
Path: .forge/skills/create-plan/SKILL.md
Commit: 6ed5d37

Reviewed: 24 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.