CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

implement-feature

Drive a researched and planned feature to a landed, tested change. Use after plan-feature has produced a docs/design/<project>/ workspace and the user says "implement it", "build the plan", "run the plan", or "let's ship this". Orchestrates refresh-plan, implement, review, a debug-local-deployment loop, and a test loop across the daytona / local-pi / claude x SDK / UI matrix, then documentation and a GitButler stacked branch. The orchestrator stays in the loop and spins narrow subagents for each phase.

Quality

91%

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

81%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 orchestration skill body: phased workflow with explicit validation loops and escalation discipline is exemplary, and commands are concrete where they exist. Weaker spots are a handful of editorializing sentences, Phases 3-4 instructing by description rather than runnable steps, and two long inline sections that would fit better as reference files.

Suggestions

Trim the justificatory asides (e.g., 'These are the things reviewers always ask for — they belong in the first draft, not after a review round.' and 'This is the highest-value hook: it is exactly the "route / debug" decision that gets lost today.') to pure imperatives.

In Phases 3-4, either inline the one or two exact commands the subagent always needs (e.g., the compose/log commands) or give the precise entry-point file in the referenced skill so the instruction is runnable without discovery.

Move the orchestration-console hook mapping and the multi-agent coordination rules into reference files (e.g., references/console-hooks.md, references/agent-coordination.md) and keep one-line pointers plus the quick-reference table in SKILL.md.

DimensionReasoningScore

Conciseness

The body is imperative and dense, assuming competence ('Plans rot.', 'You do not trust "done" without the check.') with no explanation of concepts Claude already knows. A few editorializing sentences ('These are the things reviewers always ask for...', 'This is the highest-value hook...') could be trimmed, which fits the 4 anchor (minor instances of over-explanation) rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Concrete, copy-paste commands appear where commands exist ('but branch new <type>/<feature> --anchor <parent>', 'but rub <path> <lane>', 'ruff format' then 'ruff check --fix', 'pnpm lint-fix', 'console task set <slice> --status running') plus a real resource path (.agents/skills/agent-release-gate/resources/coverage.md). Phases 3-4, however, instruct by description ('find the live port and compose project, reproduce the path') and defer exact commands to other skills, so guidance is mostly executable with minor gaps — anchor 4, not 5.

4 / 5

Workflow Clarity

Phases 0-6 are explicitly sequenced with an at-a-glance diagram, per-phase entry/exit criteria ('Exit the loop when the slice works end to end', 'Loop until the suite is green'), explicit validation checkpoints (reviewer after every implementer or fixer, retest after every fix, acceptance check per slice), and a bounded loop-discipline section with fix-now/defer/escalate triage. This matches the 5 anchor — explicit validation, feedback loops, and checklists — rather than 4.

5 / 5

Progressive Disclosure

No bundle files exist, and detail is delegated one level deep to clearly named skills (debug-local-deployment, agent-release-gate, write-pr-description) with a phase-to-skill quick-reference table. Structure is good, but the orchestration-console hooks and multi-agent coordination sections are sizable inline blocks that could live in reference files, and skill references are by name rather than links — anchor 4, not 5.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete third-person actions covering the whole orchestration scope, an explicit when-clause with four quoted user trigger phrases, and a hard plan-feature precondition that makes it highly distinct. Only conceivable nitpick is length, but every clause is informative.

DimensionReasoningScore

Specificity

The description enumerates the skill's full concrete scope — 'Orchestrates refresh-plan, implement, review, a debug-local-deployment loop, and a test loop across the daytona / local-pi / claude x SDK / UI matrix, then documentation and a GitButler stacked branch' — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4. It stays in third person ('Drive', 'Orchestrates', 'spins').

5 / 5

Completeness

Both halves are explicit: what ('Drive a researched and planned feature to a landed, tested change') and when ('Use after plan-feature has produced a docs/design/<project>/ workspace and the user says "implement it"...'). The when-clause carries concrete trigger phrases, matching the 5 anchor exactly; 4 would require the when to be less explicit.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say — "implement it", "build the plan", "run the plan", "let's ship this" — plus concrete domain anchors (plan-feature, daytona, GitButler). Coverage is comprehensive with synonymous trigger variants, so it fits the 5 anchor rather than 4.

5 / 5

Distinctiveness Conflict Risk

The hard precondition ('Use after plan-feature has produced a docs/design/<project>/ workspace') carves out a clear niche and prevents firing on generic implementation requests. Conflict risk with sibling skills is minimal, fitting the 5 anchor rather than the minor-overlap anchor at 4.

5 / 5

Total

20

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

Agenta-AI/agenta

Path

.agents/skills/implement-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.