writing-plans

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

Quality

38%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/writing-plans/SKILL.md

Quality

Content

77%

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

This is a well-structured extension skill that clearly defines its before/after hooks with concrete, actionable steps. The workflow is unambiguous with an important safety constraint (no auto-invocation of next phase). Minor weaknesses include slightly verbose explanations of edge cases (Claude Desktop vs CLI behavior) and lack of bundle files to support the referenced external skills.

Suggestions

Trim the parenthetical explanations about Claude Desktop behavior — Claude can infer when terminal operations are no-ops

Consider including or referencing the bundle paths for `devflow:phase-handoff` and `superpowers:writing-plans` so the dependency chain is navigable

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation (e.g., explaining what mark_chapter does when unavailable, explaining Claude Desktop terminal behavior). The parenthetical clarifications add some bloat but aren't egregious.	2 / 3
Actionability	Provides concrete, executable guidance: specific regex for ticket detection, exact bash command for terminal title, specific MCP tool calls and arguments, and clear naming conventions for spawned sessions. The instructions are precise enough to follow without ambiguity.	3 / 3
Workflow Clarity	Clear two-phase workflow (Before first action, After plan saved) with explicit sequencing within each phase. The constraint about NOT auto-invoking the next phase is a critical validation/safety checkpoint that's clearly stated. The handoff boundary is unambiguous.	3 / 3
Progressive Disclosure	References external skills (`superpowers:writing-plans`, `devflow:phase-handoff`, `devflow:lock-tests`) appropriately, but there are no bundle files to support these references. The skill delegates well but the reader has no way to verify or navigate to the referenced skills from this file alone.	2 / 3
	Total	10 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is extremely weak across all dimensions. It relies entirely on references to other internal skills ('superpowers:writing-plans', 'devflow') without explaining what the skill actually does, what actions it performs, or when Claude should select it. A user or Claude reading this description would have no idea what concrete task this skill accomplishes.

Suggestions

Replace internal references with a concrete explanation of what the skill does, e.g., 'Creates writing plans with structured phase transitions and handoff documentation' or similar.

Add an explicit 'Use when...' clause with natural trigger terms that describe the user scenarios where this skill should be selected.

Include specific actions the skill performs (e.g., 'generates writing outlines, manages phase transitions, produces handoff summaries') rather than describing it in terms of other skills it extends.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('extends superpowers', 'phase-handoff') without describing any concrete actions. It doesn't explain what the skill actually does in practical terms.	1 / 3
Completeness	Neither the 'what' nor the 'when' is clearly answered. The description references other skills/systems without explaining what this skill does or when it should be selected.	1 / 3
Trigger Term Quality	The terms used ('superpowers:writing-plans', 'devflow', 'phase-handoff') are internal/technical jargon that no user would naturally say. There are no natural keywords a user would use to trigger this skill.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's unclear what domain this skill operates in. Without understanding what it does, it's impossible to distinguish it from other skills, and the reference to extending another skill creates confusion about when to use this vs. the base skill.	1 / 3
	Total	4 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Commit: 8d872bf

Reviewed: 1 day 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.