writing-plans

Extends superpowers:writing-plans with devflow's phase-handoff at the end.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/writing-plans/SKILL.md

Quality

Content

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

The content is a tight, actionable workflow with strong sequencing, explicit validation, and clean structure. Minor gains are possible by tightening a few comments and resolving placeholders, but it is highly executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with inline comments that mostly justify non-obvious git decisions (e.g., stripping the 'worktree ' token to survive spaces). It is not 5 because a few explanatory comments could be trimmed further.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready bash for worktree recovery, mark_chapter calls, terminal-title setting, and phase-handoff invocation. It is not 5 because several placeholders (<Feature worktree>, <TICKET>, $ARGUMENTS) must be resolved before execution.	4 / 5
Workflow Clarity	A clear Step 0 / Before / After sequence with explicit validation (branch-identity check plus 'WORKTREE RECOVERY FAILED ... exit 1') and an error-recovery feedback loop (worktree add -> fall back to existing checkout -> re-validate). Checkpoints are explicit and the destructive worktree operation is guarded.	5 / 5
Progressive Disclosure	A short, well-organized body split into clearly signaled sections with no nested reference chains; peer-skill references (superpowers:writing-plans, devflow:phase-handoff) are one level and appropriately signaled. No bundle files are needed or present.	5 / 5
	Total	18 / 20 Passed

Description

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

The description clearly conveys the skill's extension relationship and niche but relies on plugin jargon and omits any explicit 'when to use' trigger guidance. It is distinctive but not user-trigger-friendly.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger (e.g., when writing an implementation plan that must hand off to the next devflow phase).

Replace or supplement plugin-internal jargon ('phase-handoff', 'devflow') with natural phrases a user would actually say.

List 1-2 more concrete actions the skill performs beyond 'extends' to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('writing-plans') and one concrete addition ('phase-handoff') but does not enumerate specific actions or comprehensive coverage. It falls at the 'names domain and 1-2 concrete actions' anchor rather than 4, which requires several specific actions.	3 / 5
Completeness	It states a clear 'what' ('Extends superpowers:writing-plans with devflow's phase-handoff at the end') but includes no 'Use when...' or equivalent trigger guidance, so per the rubric cap completeness cannot exceed 3. It is not 4 because the 'when' is entirely absent rather than weakly present.	3 / 5
Trigger Term Quality	The terms present ('superpowers:writing-plans', 'devflow', 'phase-handoff') are plugin-internal jargon rather than phrases a user would naturally say, with only 'writing plans' approaching a natural keyword. It sits below 3 because the common natural trigger phrases are missing.	2 / 5
Distinctiveness Conflict Risk	The description targets a narrow niche (extending a specific plugin's writing-plans with a specific phase-handoff hook), giving a clear distinct trigger with only minor overlap risk against the base writing-plans skill. It is not 5 because that overlap with the parent skill is not fully eliminated.	4 / 5
	Total	12 / 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: AndreJorgeLopes/devflow
Path: skills/writing-plans/SKILL.md
Commit: bd4b70c

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