CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

feature-planner

A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/feature-planner/SKILL.md
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.

The body delivers a clearly sequenced, highly actionable two-phase workflow with explicit checkpoints and feedback loops, written for the model without concept padding. The only weaknesses are minor redundancy in the closing guidelines section and a slightly under-specified Linear step.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no re-teaching of concepts — but the 'Important guidelines' section partially repeats guidance already stated inline (e.g., the no-visual-assumptions rule appears in both Phase 1 and the guidelines), which could be trimmed.

4 / 5

Actionability

Highly concrete guidance throughout — literal conversational scripts, named tools (Figma MCP get_design_context/get_screenshot, Read, EnterPlanMode/ExitPlanMode), a detailed plan template, and a fallback path — with one minor gap: 'Use the Linear MCP tools' leaves the actual tool invocation unspecified.

4 / 5

Workflow Clarity

The two-phase workflow is clearly sequenced with explicit validation checkpoints ('If they confirm, move to Phase 2'; 'After the plan is confirmed, create a Linear issue') and genuine feedback loops (loop back on user adjustments; fall back to a markdown file if Linear MCP is unavailable), matching the top anchor.

5 / 5

Progressive Disclosure

A single well-sectioned file with no nested or dead references and all content appropriately inline for a conversational workflow; at ~120 lines it exceeds the simple-skill threshold, and segments like the plan template or example dialogues could be moved to reference files, so it fits the 'good structure, minor organization gaps' anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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 who it serves, with an explicit manual invocation trigger and low conflict risk. Its weaker spots are thin situational trigger language and lack of synonym coverage for how users might phrase the need.

Suggestions

Add a 'Use when...' style clause naming the situations that call for the skill, e.g. 'Use when a designer or PM has a feature idea and needs it turned into an engineer-ready implementation plan.'

Include common user phrasings/synonyms as trigger terms, such as 'feature request', 'spec', 'turn an idea into a ticket', or 'plan a feature for engineering'.

Briefly enumerate the concrete workflow actions (interview the contributor, research the codebase, draft the plan, file a Linear issue) to lift specificity beyond the current two-action summary.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'describe a feature idea' and 'produce a detailed technical implementation plan for an engineer' — but stops there, matching the anchor for 1-2 concrete actions without comprehensive coverage of the workflow's sub-steps.

3 / 5

Completeness

The 'what' is clear and there is explicit trigger guidance ('Invoke manually with /feature-planner', consistent with disable-model-invocation: true), so it is not capped at 3; however the situational 'when' — what moments call for this skill — could be more specific, fitting the 4 anchor.

4 / 5

Trigger Term Quality

It contains relevant natural phrases ('feature idea', 'implementation plan', 'designers, PMs') that a user might say, but misses common variations and synonyms such as 'spec', 'turn an idea into a ticket', or 'feature request'.

3 / 5

Distinctiveness Conflict Risk

A clear niche — non-technical contributors (designers, PMs) producing an engineer-ready implementation plan — with a distinct manual trigger, so it is unlikely to fire for or be confused with other skills.

5 / 5

Total

15

/

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

coinbase/cds

Path

.claude/skills/feature-planner/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.