CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phase-handoff

Hand off between phases of the devflow new-feature pipeline. Writes a frozen-state file, marks a chapter, sets the terminal title, gates on a one-click AskUserQuestion unless `--unattended` is passed, then spawns a new session for the next phase via `mcp__ccd_session__spawn_task` so it shows up in the Claude Desktop sidebar with a deterministic title.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/phase-handoff/SKILL.md

The canonical home for this skill is phase-handoff in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 skill body is exceptionally actionable with a rigorously validated 11-step workflow — concrete commands, exact tool parameters, and full worked examples throughout. Its weaknesses are repetition of the same spawn/worktree constraints in multiple places and a monolithic single-file layout where the prompt template and example belong in separate reference files.

Suggestions

State the "spawn_task forks a fresh throwaway worktree off the default branch; the session starts cold" constraint once in the intro and reference it from steps 9-11 and the Important section instead of restating it each time.

Move the full spawn-prompt template and the MES-4282 worked example into references/spawn-prompt-template.md and reference it one level deep, keeping only the field-by-field requirements inline in step 9.

Trim the rationale commentary in step 4b and the Important section to the operative rules (never git add -A, never push, no-op vs. failure handling), which are already repeated in both places.

DimensionReasoningScore

Conciseness

Mostly efficient — the prose conveys genuinely non-obvious design rationale (worktree object-DB sharing, husky bypass reasoning) — but the core "spawn_task forks a fresh throwaway worktree off the default branch / starts cold in the wrong worktree" fact is restated in the intro, step 9's template, the worked example, step 11's output, and the Important bullets. Fits "Mostly efficient but includes some unnecessary explanation or could be tightened"; not 2 because the length is largely justified, not 4 because the near-verbatim WARNING duplication is real padding.

3 / 5

Actionability

Fully executable throughout: exact bash snippets (git rev-parse --git-common-dir, HUSKY=0 git commit --no-verify), exact tool invocations with parameter shapes (mark_chapter {title, summary}; spawn_task title/tldr/prompt), deterministic title formats with worked examples ([MES-4282] [MR#29] Implementation), exact output text, and a complete MES-4282 sample prompt. Copy-paste ready and covers the common cases.

5 / 5

Workflow Clarity

Eleven clearly sequenced steps with explicit validation at every fragile point: STOP if on the default branch (step 1), guarded no-op vs. loud WARNING commit-failure distinction (step 4b), re-entry append semantics, a one-click user gate with --unattended/--no-handoff escape hatches (step 10), and orphan-worktree pruning guidance. Matches the anchor with explicit validation steps and feedback loops for error recovery.

5 / 5

Progressive Disclosure

The body has section structure (## Steps, ## Important) but no bundle files exist and everything is inline across ~290 lines; the full prompt template and the ~40-line worked example are content that clearly belongs in a one-level-deep references/ file. Fits "Some structure but could be better organized; content that should be separate is inline"; not 4 given zero reference files at this length.

3 / 5

Total

16

/

20

Passed

Description

67%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 highly specific and action-oriented with excellent distinctiveness, fully describing what the skill does in third-person voice. Its main weaknesses are the complete absence of an explicit "Use when..." trigger clause and a reliance on internal tooling jargon over natural user phrases.

Suggestions

Append an explicit trigger clause, e.g. "Use when a devflow phase (spec, plan, lock-tests) completes and the next phase must start in a fresh session, or when the user says 'handoff' or 'next phase'."

Replace or supplement internal tool names (mcp__ccd_session__spawn_task, AskUserQuestion) with natural trigger terms like "phase handoff", "phase transition", or "spawn next phase session" that a user would actually say.

Trim the mechanism detail (e.g. the --unattended exception and sidebar specifics) to leave room for the missing when-to-use guidance within a comparable length.

DimensionReasoningScore

Specificity

Quotes five concrete actions — "Writes a frozen-state file, marks a chapter, sets the terminal title, gates on a one-click AskUserQuestion", "spawns a new session for the next phase via mcp__ccd_session__spawn_task" — comprehensively covering the skill's behavior in third-person voice. Score 4 rejected because there are no real coverage gaps; every capability is explicitly named.

5 / 5

Completeness

The "what" is explicit and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance; "when" is only weakly implied by "Hand off between phases". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords like "Hand off", "phases", "devflow new-feature pipeline", "new session" are relevant but lean on internal proper nouns (mcp__ccd_session__spawn_task, AskUserQuestion) rather than natural user phrasing, and miss common variations such as "handoff" or "phase transition". Fits the anchor "Some relevant keywords but missing common variations or synonyms".

3 / 5

Distinctiveness Conflict Risk

"devflow new-feature pipeline", phase names, and tool-specific references (spawn_task, chapter marking, Claude Desktop sidebar) carve out a clear niche with minimal overlap risk against any other skill. Matches the anchor "Clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

16

/

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/phase-handoff/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.