agile-product-owner
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill agile-product-owner73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its domain (agile product ownership), lists specific capabilities, and provides explicit trigger conditions. The use of domain-specific terminology like 'INVEST-compliant' and 'velocity tracking' creates clear distinctiveness. The description uses proper third-person voice and maintains good conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (INVEST-compliant user story generation, sprint planning, backlog management, velocity tracking) AND when ('Use for story writing, sprint planning, stakeholder communication, and agile ceremonies'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'user story', 'sprint planning', 'backlog', 'velocity tracking', 'story writing', 'stakeholder communication', 'agile ceremonies' - good coverage of common agile/product terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Senior Product Owner role with specific agile/scrum terminology like 'INVEST-compliant', 'velocity tracking', 'agile ceremonies' - unlikely to conflict with general project management or development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and avoids explaining concepts Claude knows, but lacks actionable depth. It mentions scripts and features without showing concrete examples of inputs, outputs, or workflows. The absence of a clear multi-step process for product ownership tasks (epic breakdown → story validation → sprint planning) limits its practical utility.
Suggestions
Add a concrete workflow showing the sequence: define epic → generate stories → validate INVEST → plan sprint → track velocity, with validation checkpoints
Include example input (an epic description) and example output (generated user story with acceptance criteria) to make the tool actionable
Add links to detailed documentation files for advanced features like velocity tracking metrics or backlog prioritization strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, listing capabilities and usage without explaining what agile, user stories, or INVEST criteria are—concepts Claude already knows. | 3 / 3 |
Actionability | Provides specific CLI commands for the scripts, but lacks executable code examples, sample inputs/outputs, or concrete examples of generated user stories and acceptance criteria. | 2 / 3 |
Workflow Clarity | No workflow sequence is provided for how to use these tools together (e.g., epic → stories → sprint planning). Missing validation steps or feedback loops for reviewing generated stories. | 1 / 3 |
Progressive Disclosure | Content is brief and organized with clear sections, but references scripts without linking to detailed documentation or examples. No clear navigation to advanced features or reference materials. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
- 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.