feat-dev

End-to-end workflow for implementing a non-trivial qwen-code feature. Covers requirements investigation, design, E2E test planning, baseline dry-run, implementation, verification, self-audit, code review, and iteration.

Quality

72%

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 ./.qwen/skills/feat-dev/SKILL.md

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.

The body is a well-sequenced, actionable workflow with strong validation feedback loops and clean phase structure. It is concise and executable, with only minor opportunities to externalize templates or trim framing prose.

Dimension	Reasoning	Score
Conciseness	The body is efficient — each phase is a tight bullet list with an explicit 'Output:' line and no padding of concepts Claude already knows; not a 5 because a few framing sentences ('Do not combine phases; the output of each phase feeds the next') could be trimmed.	4 / 5
Actionability	Provides concrete, executable guidance — artifact paths ('docs/design/<feature>.md'), real commands ('npm run build', 'npm run typecheck', 'npm run bundle', 'node dist/cli.js'), and named skills/agents — with only minor gaps such as the design-doc structure being a bullet list rather than a template.	4 / 5
Workflow Clarity	Eight phases are clearly sequenced, each with an 'Output:' checkpoint, plus explicit validation feedback loops ('re-test until all groups pass', 'until two consecutive clean passes') and bounded iteration rules, matching the top anchor.	5 / 5
Progressive Disclosure	Well-organized into clearly headed phases with no nested references and no inlined material that clearly belongs in separate bundle files (none exist); not a 5 because the design-doc and test-plan templates could optionally live in reference files to keep the overview leaner.	4 / 5
	Total	17 / 20 Passed

Description

63%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 and comprehensively states what the skill does across all phases, but omits any explicit 'when to use it' trigger guidance, which caps completeness and dampens trigger-term quality and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when implementing a non-trivial qwen-code feature that needs design, behavioral validation, or coordinated multi-file changes.'

Include natural user synonyms such as 'build', 'add', or 'ship a feature' alongside 'implementing'.

Lead with the trigger condition before the phase list so the 'when' is as prominent as the 'what'.

Dimension	Reasoning	Score
Specificity	Names the domain and lists many concrete actions — 'requirements investigation, design, E2E test planning, baseline dry-run, implementation, verification, self-audit, code review, and iteration' — giving comprehensive coverage of the workflow phases.	5 / 5
Completeness	The 'what' is clearly answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3 even though the capability list is thorough.	3 / 5
Trigger Term Quality	Contains some natural terms ('implementing a feature', 'code review', 'design') but leans on process jargon ('baseline dry-run', 'self-audit') and misses common synonyms or an explicit trigger phrase; not a 4 because natural-user variations are sparse.	3 / 5
Distinctiveness Conflict Risk	Scoped to 'a non-trivial qwen-code feature' with a multi-phase workflow, making it mostly distinct with only minor overlap risk against general coding skills; not a 5 because the absent trigger clause weakens distinctiveness.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: QwenLM/qwen-code
Path: .qwen/skills/feat-dev/SKILL.md
Commit: 054eabb

Reviewed: 1 day 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.