writing-plans

Write self-contained implementation plan files that a fresh, possibly weaker executor can run without the author's context — splitting work into PR-sized plans, with verification gates, STOP conditions, and a memo protocol for design forks. Use when asked to write/create a plan, turn a decided design or ticket into plans, or when another skill hands off plan-writing. Not for deciding what to build or executing plans.

Quality

96%

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

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

An exemplary instruction-only skill body: dense and assumption-respecting, with concrete naming patterns, a deterministic decision procedure, embedded verification/feedback loops, and clean progressive disclosure into verified reference templates. No meaningful weaknesses to flag.

Dimension	Reasoning	Score
Conciseness	Lean and dense with no padding and no explanation of concepts Claude already knows; assumes competence (does not define PR, VCS, or verification gates) while every evocative phrase like 'context dies at the session boundary' carries load-bearing intent.	5 / 5
Actionability	Gives concrete, executable guidance — a deterministic destination-resolution order, '$AGENTS_PLANS_DIR', '<destination>/<slug>.md' and 'NNN-<step-slug>.md' naming, an explicit recon checklist, and template pointers — fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	Clearly sequenced (Where plans go → Recon → Decomposition → Layout → Writing → Memos → Re-entry) with explicit validation checkpoints — per-step verification gates, STOP-condition feedback loops, a revision drift check, and a reconcile-on-re-entry protocol.	5 / 5
Progressive Disclosure	The body is a concise overview pointing to three real, one-level-deep template references (plan-template.md, index-template.md, memo-template.md) via well-signaled links, with detail appropriately split out and easy navigation.	5 / 5
	Total	20 / 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 capabilities and explicit trigger conditions with a useful negative-boundary clause. Trigger-term coverage is good but leaves a few natural phrasings unsaid, keeping it just short of perfect.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Write self-contained implementation plan files', 'splitting work into PR-sized plans, with verification gates, STOP conditions, and a memo protocol for design forks' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Write self-contained implementation plan files… with verification gates, STOP conditions, and a memo protocol') and when ('Use when asked to write/create a plan, turn a decided design or ticket into plans, or when another skill hands off plan-writing'), with concrete trigger phrases and a 'Not for…' boundary.	5 / 5
Trigger Term Quality	Captures natural phrases users would say — 'asked to write/create a plan', 'turn a decided design or ticket into plans', 'another skill hands off plan-writing' — with good synonym coverage, but a few natural variants ('plan out the work', 'break down work') are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear plan-writing niche and explicitly disambiguates it from adjacent skills via 'Not for deciding what to build or executing plans', minimizing conflict risk.	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: joshuadavidthomas/agent-skills
Path: writing-plans/SKILL.md
Commit: 516dee7

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