CtrlK
BlogDocsLog inGet started
Tessl Logo

executing-plans

Devflow wrapper for the upstream executing-plans skill. Use when you have a written implementation plan to execute task-by-task. ALWAYS invoke `/devflow:executing-plans` rather than the upstream skill directly — this wrapper guarantees that the post-implementation handoff goes to `/devflow:finish-feature` (devflow's verification + PR/MR creation flow) instead of `superpowers:finishing-a-development-branch` (the upstream default, which doesn't integrate with devflow's VCS-coherent finish flow).

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written orchestration wrapper with executable, validated workflows and clear phase sequencing. The only mild gap is that the Step 0 recovery bash is substantial enough that it might warrant its own reference file.

DimensionReasoningScore

Conciseness

Mostly lean with executable bash and terse rationale, but a few restated-purpose sentences and verbose inline correctness comments could be trimmed without losing clarity.

4 / 5

Actionability

Step 0 provides copy-paste-ready bash with real error handling and a fallback branch, and the handoff phases specify concrete skill names and status values (DONE, DONE_WITH_CONCERNS, BLOCKED, NEEDS_CONTEXT).

5 / 5

Workflow Clarity

Clear Step 0 → Phase 0 → Phase 1 → Phase 2 sequence with explicit validation (branch-show-current check, WORKTREE RECOVERY FAILED exit) and recovery feedback loops, plus an edge-case section.

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases with no nested references, but at ~80 lines it exceeds the simple-skill threshold and the sizeable inline Step 0 bash could justify offloading.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states both purpose and trigger, with explicit disambiguation from the upstream skill. It is slightly weighted toward internal routing mechanics over natural user vocabulary.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions (intercepts terminal handoff, routes to finish-feature, runs verification, creates PR/MR, retains learnings), but they read as internal wrapper mechanics rather than a comprehensive user-facing action list.

4 / 5

Completeness

Explicitly answers both what (devflow wrapper forcing the finish-feature handoff) and when (written implementation plan to execute task-by-task) with a concrete trigger clause.

5 / 5

Trigger Term Quality

Includes a natural trigger phrase ('Use when you have a written implementation plan to execute task-by-task') but leans heavily on internal skill-path names rather than broad natural synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (intercepting the upstream finish handoff) and explicitly disambiguates from the upstream executing-plans skill, keeping conflict risk minimal.

5 / 5

Total

18

/

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.

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.