CtrlK
BlogDocsLog inGet started
Tessl Logo

po-feature-spec

Skill do Product Owner para especificação de features. Use quando precisar definir requisitos de negócio, escrever user stories, critérios de aceitação, priorização de backlog, ou qualquer documento de especificação de produto. Inclui fundamento de negócio para discovery: validação de hipótese, problema vs. necessidade, MVP, modelo de monetização e métricas pirata (AARRR) como input da spec. Trigger em: "nova feature", "especificação", "user story", "requisito", "backlog", "PO", "definir escopo", "critério de aceitação", "MVP", "roadmap", "validação de hipótese", "discovery", "monetização", "pricing", "product-market fit", "métricas AARRR".

69

Quality

83%

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

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.

The content is well-structured, actionable, and covers the PO feature-spec workflow thoroughly with concrete formulas, thresholds, and validation gates. Its main weakness is conciseness — the business-foundation section over-explains concepts Claude already knows.

Suggestions

Trim the 'Fundamento de Negócio' section: replace the book-derived theory explanations (MVP definition, Maslow, freemium economics, startup phases) with concise bullets, since Claude already knows these concepts.

Tighten the ideation-frameworks section by either inlining a concrete template for the recommended JTBD → HMW → SCAMPER → First Principles order or moving it entirely to the referenced guide.

Ensure referenced files (policies/vertical-slices.md, templates/deep-interview.md, docs/skill-guides/*) are bundled under references/ or clearly noted as external repo-consumer paths, so the progressive-disclosure links are verifiable.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the 'Fundamento de Negócio' section explains business concepts Claude already knows (Maslow's pyramid, MVP definition, freemium economics, startup phases) at length, which is more than minor padding.

3 / 5

Actionability

Provides concrete executable guidance — the prioritization formula with lookup tables, ambiguity formula with thresholds and MCP tool, and DADO/QUANDO/ENTÃO examples — with minor gaps where some sections (ideation frameworks) only name methods without concrete templates.

4 / 5

Workflow Clarity

Clear sequenced workflow from inputs through structure, ambiguity scoring, deep interview, and handoffs, with validation checkpoints (ambiguity > 0.7 → interview, stability ratio, readiness gate); minor gaps because validation is largely policy-referenced rather than self-contained.

4 / 5

Progressive Disclosure

Good structure with one-level-deep, clearly signaled references to external files (skill-guides, policies/vertical-slices.md, templates/deep-interview.md); however no bundle files exist in references/scripts/assets, so the referenced paths point outside the skill bundle and cannot be verified.

4 / 5

Total

15

/

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.

The description is strong: it concisely states what the skill does, when to use it, and lists comprehensive concrete trigger terms in the third person. It clearly carves out a distinct PO feature-specification niche.

DimensionReasoningScore

Specificity

Lists multiple concrete PO actions — 'definir requisitos de negócio', 'escrever user stories', 'critérios de aceitação', 'priorização de backlog', 'validação de hipótese', 'modelo de monetização', 'métricas pirata (AARRR)' — with comprehensive coverage matching the top anchor.

5 / 5

Completeness

Explicitly answers both 'what' (Skill do Product Owner para especificação de features, with listed deliverables) and 'when' ('Use quando precisar...'), with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Provides an explicit 'Trigger em:' list with natural user phrases and synonyms — 'nova feature', 'user story', 'backlog', 'PO', 'MVP', 'pricing', 'product-market fit', 'métricas AARRR' — covering synonyms and variations as the top anchor requires.

5 / 5

Distinctiveness Conflict Risk

Targets a clear PO/product-specification niche with PO-specific triggers ('user story', 'critério de aceitação', 'AARRR'), making it distinguishable with minimal conflict risk against other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
felvieira/claude-skills-fv
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.