CtrlK
BlogDocsLog inGet started
Tessl Logo

implement-plan

Implements an existing plan file via gated, context-isolated sub-agents. User-invoked only: /implement-plan <plan-file> [PRD_FILE=...] [ADR_FILES=...]. Orchestrates TDD-gated lanes (RED, GREEN, review+fix, independent verify), freezes cross-lane contracts before fan-out, scouts each lane once into a shared brief, treats the plan as a living artifact updated from sub-agent feedback, and maintains an evidence-based progress ledger. Produces implemented, reviewed, independently verified code plus an as-built plan file.

71

Quality

88%

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

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.

An exemplary orchestration skill body: a tightly sequenced, evidence-gated workflow with concrete commands, explicit feedback loops, and clean progressive disclosure into two real reference files. The only nit is a few justificatory 'Why:' passages that slightly pad the token budget.

DimensionReasoningScore

Conciseness

Dense and purposeful with no basic-concept padding and clear role framing, but the inline 'Why:' rationale paragraphs (e.g., on evidence and concurrency) are minor over-explanation that could be trimmed while keeping the actionable core.

4 / 5

Actionability

Concrete directives throughout — '/code-review --fix' (effort high/xhigh), exact model assignments (sonnet/haiku/session), real file references, and invocation examples — with exact role recipes delegated to existing reference files, giving fully executable guidance.

5 / 5

Workflow Clarity

Explicit fixed sequence (Step −1 → freeze → scouts → fan-out → per-phase loop → integration → whole-diff → acceptance) with evidence-based NON-NEGOTIABLE GATES, feedback loops on FAIL, and a DONE checklist.

5 / 5

Progressive Disclosure

Overview body with well-signaled one-level-deep references to real files ('references/role-prompts.md', 'references/templates.md'), with role-prompt and template detail appropriately split out and clearly signaled for navigation.

5 / 5

Total

19

/

20

Passed

Description

83%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 highly specific, well-targeted description that comprehensively states capabilities and gives an explicit invocation trigger. The main weakness is a technical-leaning trigger vocabulary and a command-style 'when' rather than a natural scenario phrase.

Suggestions

Add a natural-language 'Use when...' clause naming the triggering situation (e.g., 'Use when the user has a completed plan file to implement'), so the 'when' is scenario-based rather than only command syntax.

Soften jargon in the trigger zone with common synonyms (e.g., 'execute/run a plan file') alongside the technical lane/TDD terms to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Orchestrates TDD-gated lanes (RED, GREEN, review+fix, independent verify)', 'freezes cross-lane contracts before fan-out', 'scouts each lane once into a shared brief', 'maintains an evidence-based progress ledger' — with comprehensive coverage and no vague fluff.

5 / 5

Completeness

Clearly answers 'what' (orchestrates plan implementation via gated sub-agents) and gives explicit trigger guidance ('User-invoked only: /implement-plan <plan-file>'), but the 'when' is a command syntax rather than a spelled-out situational scenario.

4 / 5

Trigger Term Quality

Natural triggers like 'implement-plan', 'plan file', 'PRD_FILE', and 'ADR_FILES' are present and prominent, but coverage leans technical (TDD-gated lanes, fan-out) and is missing common synonyms a user might say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (plan-execution orchestration via TDD-gated, context-isolated sub-agents) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
MrToxy/claude-skills
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.