product-capability

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.

Quality

75%

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 ./skills/product-capability/SKILL.md

Quality

Content

67%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 well-structured, actionable planning skill with a clear workflow and a concrete output template. Its main weaknesses are motivational padding and a lack of explicit validation checkpoints or a worked example.

Suggestions

Remove motivational filler (e.g. 'These are the things that often live only in senior-engineer memory', 'If this statement is weak, the implementation will drift') to tighten the body.

Add an explicit validation checkpoint in the workflow — e.g. after step 3, require confirming that every fixed rule is labeled fixed/preference/open before producing the handoff.

Include one short worked example of a completed CAPABILITY/CONSTRAINTS/CONTRACT output to make the template copy-paste concrete.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded with motivational asides ('These are the things that often live only in senior-engineer memory', 'If this statement is weak, the implementation will drift', 'The goal is not to create another planning stack. The goal is ...') that could be trimmed without losing guidance.	3 / 5
Actionability	Provides a concrete 4-step workflow, an explicit ordered output-format template, enumerated constraint and contract fields, and named next-lane handoffs; minor gap is the absence of a worked example showing a filled-in artifact.	4 / 5
Workflow Clarity	Steps are clearly sequenced (restate → resolve constraints → define contract → translate/handoff) with a tri-state handoff classification, but there are no explicit validate-and-retry checkpoints; the 'open questions blocking implementation' field is only an implicit checkpoint.	4 / 5
Progressive Disclosure	Well organized into labeled sections with a single one-level-deep reference ('docs/examples/product-capability-template.md'), but no bundle directory exists so the referenced template path is unverified and a fair amount of reference-style material is inlined.	4 / 5
	Total	15 / 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 strong description that clearly states the capability and when to use it, with concrete deliverables and explicit trigger guidance. It is slightly held back by jargon ('ECC-native', 'PRD-to-SRS lane') that limits how naturally users would phrase the trigger.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete deliverable actions ('exposes constraints, invariants, interfaces, and unresolved decisions'), but the actions all describe one transformation rather than a breadth of operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Translate ... into an implementation-ready capability plan that exposes ...') and when ('Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ('PRD intent, roadmap asks, product discussions', 'capability plan', 'SRS') that a product or engineering user would say, though jargon like 'ECC-native PRD-to-SRS lane' narrows the natural phrasing surface.	4 / 5
Distinctiveness Conflict Risk	The 'ECC-native PRD-to-SRS lane' framing carves a clear niche with mostly distinct triggers, with only minor overlap risk against general planning or spec-writing skills.	4 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/product-capability/SKILL.md
Commit: d8409a4

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.