CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fast-feature

Use when driving a single already-specced ticket through devflow in one session, unattended, resolving ambiguity from the codebase rather than by asking, then spec, plan, and lock-tests back-to-back with an independent reviewer standing in for the human gate, spawning a new session only for the execute phase. Also the per-ticket driver that orchestrate-epic invokes.

Quality

86%

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

The canonical home for this skill is fast-feature in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 strong operational runbook with an exceptionally clear step sequence, explicit STOP conditions, and real feedback loops — the unattended workflow design is unambiguous. Its weaknesses are redundancy (the one-spawn and never-self-approve rules each appear several times, and Common Mistakes overlaps the Red flags table) and a reviewer-subagent dispatch that describes rather than scripts the gate.

Suggestions

Merge the Common Mistakes and Red flags sections into one — they cover the same failure modes (asking when the codebase answers, self-approving tests, letting an intermediate phase spawn) in slightly different phrasings, saving ~15 lines.

State the one-spawn rule once in the Core principle and reference it from Steps 3, 4, and 6 instead of restating the rationale at each step.

Provide the Step 5 reviewer subagent's prompt verbatim (or a template) so the approval gate is dispatched exactly the same way on every run rather than assembled from a description.

DimensionReasoningScore

Conciseness

The body is operational and free of explanations of known concepts, but the one-spawn rule is restated in the intro, core principle, Steps 3/4/6, Common Mistakes, Red flags, and Important, and the Common Mistakes and Red flags sections largely duplicate each other ("Stopping to ask when the codebase already answers it" vs "The ACs are clear but I'll ask anyway to be safe").

3 / 5

Actionability

Mostly executable: the worktree creation bash block is copy-paste ready, the ticket-key regex and exact phase-handoff invocations are concrete. Minor gaps remain — the Step 5 reviewer subagent dispatch is described but no ready-to-use prompt is given, and placeholders like `<short-kebab-summary>` and `<resolved main clone>` are underspecified.

4 / 5

Workflow Clarity

Steps 0–6 are clearly sequenced with a mermaid overview and explicit validation checkpoints throughout: branch confirmation with a STOP on mismatch, the ambiguity decision tree with human-only forks as blockers, the reviewer gate with a NEEDS_WORK fix-and-re-dispatch loop and a two-strike stop, and worktree-creation failure handling.

5 / 5

Progressive Disclosure

A single-file skill with no bundle references, but the content is a coherent operational runbook organized into well-labeled numbered steps and sections that are easy to navigate. At ~139 lines with everything inline and some cross-section redundancy, structure is good rather than optimal.

4 / 5

Total

16

/

20

Passed

Description

92%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 dense, precise description that explicitly covers what the skill does, when to use it, and how it differs from the standard multi-spawn devflow pipeline. Its only weakness is heavy reliance on project-specific jargon with no synonyms, which is acceptable for a suite-internal skill but slightly narrows natural triggering.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the entire pipeline — "resolving ambiguity from the codebase rather than by asking", "spec, plan, and lock-tests back-to-back", "independent reviewer standing in for the human gate", "spawning a new session only for the execute phase" — with no gaps in coverage of the workflow's stages.

5 / 5

Completeness

It explicitly answers both questions: the "Use when driving a single already-specced ticket through devflow in one session, unattended" clause gives concrete trigger conditions, and the "what" fully enumerates the pipeline from ambiguity resolution through the single execute spawn.

5 / 5

Trigger Term Quality

Good natural keyword coverage within the devflow ecosystem ("already-specced ticket", "devflow", "in one session", "unattended", "execute phase", "orchestrate-epic"), but the terms are project jargon with no synonyms or common variations ("lock-tests", "specced" assume deep suite familiarity).

4 / 5

Distinctiveness Conflict Risk

A clear niche (already-specced ticket, single session, unattended, spawn only at execute) with triggers distinct from the standard devflow phases, and the stated relationship to orchestrate-epic further disambiguates it from sibling skills.

5 / 5

Total

19

/

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/fast-feature/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.