CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-plans

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

Quality

78%

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

Fix and improve this skill with Tessl

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

The canonical home for this skill is writing-plans in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a well-crafted extension skill: it assumes the base skill, inlines only operational deltas, and backs every fragile operation (worktree recovery, chapter marking, terminal titling) with executable code, validation, and failure fallbacks. Its only weakness is mild comment verbosity in the bash block.

DimensionReasoningScore

Conciseness

The body is dense and operational with no concept explanations Claude already knows — every section is a concrete addition ('Step 0 — Re-establish the feature worktree', 'Invoke devflow:phase-handoff with arguments --phase plan --next-phase lock-tests'). Minor over-explanation remains in inline rationale comments ('(`[ -d ]` alone would skip recovery for a stale non-worktree dir or a detached/wrong-branch checkout.)', '(not awk $2) so worktree paths containing spaces survive') that could be trimmed slightly, so it sits just below the lean-everywhere anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: a complete bash worktree-recovery script with placeholders sourced from the handoff block, a concrete regex ('[A-Z]+-[0-9]+'), a literal mark_chapter payload, an exact printf escape sequence, and exact invocation arguments ('--phase plan --next-phase lock-tests'). Not level 4 territory because no key execution detail is missing — even the spawned-session title format is specified.

5 / 5

Workflow Clarity

Sequencing is explicit and event-anchored ('do this before anything else', 'Before: First action of the skill', 'After: Plan saved to disk'), with a hard validation checkpoint and error path in the script: the branch-validity guard plus '[ "$on" = "$feature_branch" ] || { echo "WORKTREE RECOVERY FAILED..."; exit 1; }'. It also includes recovery fallbacks (reusing an existing checkout when worktree add fails) and graceful degradation (skip mark_chapter silently if unavailable), matching the feedback-loop anchor.

5 / 5

Progressive Disclosure

The skill is itself a thin delta layer: it delegates the entire base workflow to 'superpowers:writing-plans' and 'devflow:phase-handoff' and inlines only the additions, which is exactly the appropriate split. What remains inline (~55 lines) is operational content that must be present, organized under clear headers, with no nested references — no references/, scripts/, or assets/ exist in the bundle, and nothing inlined belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

53%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 is accurate and honest about being a delta skill, and it is appropriately specific about what it adds, but it is written for a reader who already knows the devflow/superpowers ecosystem rather than for trigger matching. It lacks any 'Use when...' guidance and natural-language trigger phrases, leaving a user-facing invocation path largely implicit.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when writing an implementation plan for a devflow-managed ticket or when a phase-handoff should follow planning') to remove the completeness cap.

Include natural trigger phrases a user would actually say — 'write an implementation plan', 'plan this feature', 'hand off after planning' — instead of relying solely on the skill names 'superpowers:writing-plans' and 'phase-handoff'.

Spell out one or two more concrete actions beyond the handoff addition (e.g. worktree re-establishment, chapter marking) so the capability list reads comprehensively rather than as a single delta.

DimensionReasoningScore

Specificity

Phrases like 'Extends superpowers:writing-plans with devflow's phase-handoff at the end' name the domain and one concrete action (adding phase-handoff at the end), matching 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above level 2 ('actions are minimal or generic') because the extension action and its placement are concrete, but below level 4 since only a single action is listed.

3 / 5

Completeness

The 'what' is clear (extends writing-plans with a phase-handoff at the end) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines — 'when' is only weakly implied through the reference to the base skill. It cannot reach 4, which requires both 'what' and an explicit 'when'.

3 / 5

Trigger Term Quality

Relevant keywords exist — 'writing-plans', 'phase-handoff', 'devflow' — but they are skill names and internal jargon rather than the natural phrases a user would say ('write an implementation plan', 'plan the next phase'), and common variations and synonyms are absent. This sits at 'Some relevant keywords but missing common variations or synonyms', not level 4 which requires genuinely natural term coverage.

3 / 5

Distinctiveness Conflict Risk

Naming two specific skills ('superpowers:writing-plans', 'devflow:phase-handoff') gives it a clear niche with mostly distinct triggers — 'Mostly distinct; minor overlap risk with closely related skills'. It cannot score 5 because its triggers are inherently identical to the base writing-plans skill it extends, so a plan-writing request could pull in either.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

devflow-plugin/skills/writing-plans/SKILL.md

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.