CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

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

57

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 lean, highly actionable instruction set with concrete tool calls, exact arguments, and a clear two-phase sequence. Its only weakness is workflow_clarity: the steps lack explicit validation/verification checkpoints for the spawn and phase-handoff operations.

Suggestions

Add an explicit verification step after invoking devflow:phase-handoff (e.g., confirm the frozen-state file was written and the spawned session is visible) with a fix-and-retry loop if it fails.

Replace the silent '|| true' fallback in the bash snippet with a condition that logs or reports when the window title could not be set, so a failed signal is not silently swallowed.

Add a brief 'Verify' checklist at the end of each phase confirming the expected side effects occurred before declaring the phase complete.

DimensionReasoningScore

Conciseness

At ~25 lines every line is instructive — regex, a bash snippet, exact tool calls and arguments — with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides concrete executable guidance — a regex pattern, a runnable bash one-liner, exact tool names (mark_chapter, devflow:phase-handoff, mcp__ccd_session__spawn_task) with argument strings, and an explicit 'Do NOT auto-invoke' guardrail — fully copy-paste-ready, matching the level-3 anchor.

3 / 3

Workflow Clarity

Two clearly sequenced phases ('Before'/''After') with numbered steps are present, but there are no explicit validation/verification checkpoints (the bash step uses a silent '|| true' no-op rather than a validate-and-fix loop), matching the 'steps listed but checkpoints missing or implicit' anchor rather than the level-3 feedback-loop anchor.

2 / 3

Progressive Disclosure

It is a single-purpose skill under 50 lines with no bundle files and is organized into clearly labeled 'Before'/'After' sections, which per the simple-skills note can score 3 with just well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

42%

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 identifies a precise niche by referencing its parent skill and the specific behavior it adds, but it relies on internal technical jargon rather than natural trigger terms and never tells Claude when to use it. It is concise but lacks the 'Use when...' guidance that would make it discoverable.

Suggestions

Add an explicit 'Use when...' clause stating when this skill should activate (e.g., 'Use when writing an implementation plan as part of a devflow phase-handoff').

Replace internal skill-name jargon with natural user-facing trigger terms so the description matches what a user would actually say.

Optionally enumerate the concrete actions it adds (e.g., ticket detection, window-title setting, phase-handoff invocation) to lift specificity from 2 to 3.

DimensionReasoningScore

Specificity

It names the domain ('superpowers:writing-plans') and a concrete action ('Extends...with devflow's phase-handoff at the end'), but does not list multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It states what the skill does ('Extends superpowers:writing-plans with devflow's phase-handoff') but never states when Claude should use it; the 'when' is entirely missing, so it sits at the 'has what, but when is missing' anchor rather than the explicit-trigger level 3.

2 / 3

Trigger Term Quality

The only keywords are internal skill names ('writing-plans', 'phase-handoff') — technical jargon a user would not naturally say when they need this, with no natural trigger terms, matching the 'no natural keywords; technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

Tying the description to a specific parent skill ('superpowers:writing-plans') plus a specific additive behavior ('devflow's phase-handoff') gives it a clear niche unlikely to trigger the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AndreJorgeLopes/devflow
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.