implement-feature

Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-triforce/skills/implement-feature/SKILL.md

Quality

Content

56%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 body is concise and well-structured with a clearly sequenced multi-step workflow and explicit checkpoints, but its actionability is limited because the named checklists that drive the actual execution are referenced but never defined in the (empty) bundle.

Suggestions

Define the referenced checklists (SIGN IN, TIME OUT 1/2, Pre-Delivery, SIGN OUT) inline or as actual reference files in the bundle so the steps are fully executable.

Add a brief validation gate description for each TIME OUT checkpoint (e.g., what must be verified before proceeding) to make the feedback loops explicit.

If checklists live elsewhere, link them explicitly (e.g., 'See references/sign-in-checklist.md') so progressive disclosure navigation is complete.

Dimension	Reasoning	Score
Conciseness	The body is lean with short, well-separated sections and no tutorials on concepts Claude already knows; only minor redundancy between the intro and the numbered steps keeps it just below fully efficient.	4 / 5
Actionability	Concrete scaffolding exists (8 numbered steps, named checklists, paths like src/ and tests/, example commands), but the referenced checklists (SIGN IN, TIME OUT, Pre-Delivery) are not defined anywhere in the bundle, leaving key execution details incomplete.	3 / 5
Workflow Clarity	A clear 8-step sequence with two explicit TIME OUT checkpoints plus SIGN IN/SIGN OUT brackets the process, but the validation content of those checkpoints is named rather than shown, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Sections are well-organized and the skill is small enough not to need external files, but named checklists are referenced without being defined or linked, leaving a small navigation/structure gap.	4 / 5
	Total	15 / 20 Passed

Description

56%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 clearly states what the skill does and names several concrete actions, but it lacks an explicit 'Use when...' trigger and relies on somewhat generic action verbs, leaving trigger coverage and completeness as the weakest dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when implementing an approved feature spec or translating product requirements into code'.

Broaden trigger terms with user-natural synonyms such as 'implement a feature', 'build a feature', 'write code from a spec'.

Tighten the action list with more specific verbs (e.g. 'designs architecture and creates an ADR', 'writes unit and integration tests') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Reads the spec, designs architecture, writes code and tests') but they remain somewhat generic rather than comprehensive, fitting the anchor for minor gaps in coverage.	4 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause; per the rubric guideline a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant domain keywords ('feature', 'specification', 'architecture') are present but common natural variations users would say ('implement/build a feature', 'write code from a spec') are missing.	3 / 5
Distinctiveness Conflict Risk	The 'feature from its specification' framing plus delegation to the 'Forja (Dev) agent' gives it a mostly distinct niche with only minor overlap risk against closely related coding skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/agent-triforce/skills/implement-feature/SKILL.md
Commit: ac92f1d

Reviewed: ~12 hours ago

Table of Contents

Discovery Implementation Validation

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.