agile-product-owner

Looking at how you've structured the PO guidance around sprint cycles and stakeholder management—I noticed the spec coverage could use some reinforcement in a few key areas, but the practical focus is solid.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 67/100, D grade territory. This is based on Anthropic's 5-pillar framework for evaluating agentic skills. Your strongest area is Spec Compliance (12/15)—the YAML structure is solid—but Progressive Disclosure Architecture (16/30) is dragging the score down. The gap between "working implementation" and "well-structured skill" is costing you roughly 25 points.

What's Working Well

• Valid YAML frontmatter - You've got the required fields correct and properly formatted (5/5 on spec compliance)
• Real problem-solving focus - INVEST criteria validation, sprint planning with capacity, velocity tracking actually address what product owners need
• Working implementation - The Python script provides tangible value rather than just theory
• Decent metadata baseline - "agile-product-owner" follows naming conventions and your description hits real product owner activities

The Big One: Architecture Is Backwards

Your biggest issue is treating the Python script like a reference document when it should be implementation detail. Right now you're describing script features (lines 17-31) in SKILL.md, which wastes token budget and buries the actual skill workflow.

Here's the fix:

1. Create references/workflows.md with user-facing workflows (Story Generation, Sprint Planning, Backlog Prioritization)
2. Keep implementation details in the script—don't explain them in SKILL.md
3. Add a TOC since this will be >100 lines of real content
4. Move the Features section into concrete workflow steps users follow

This restructuring alone gets you +6 points toward PDA.

Other Things Worth Fixing

1. Add trigger patterns to description - Replace "Use for story writing, sprint planning..." with actual triggers: 'write user story', 'create acceptance criteria', 'plan sprint', 'estimate story points'. Helps discoverability (+4 points).

2. No example templates - Add a simple "Story Templates" section showing: "As a [persona], I want [action] so that [benefit]" with a Given/When/Then acceptance criteria example. Users shouldn't have to guess the format (+3 points).

3. Workflow clarity missing - Number your core workflows (1. Collect epic details → 2. Break down scope → 3. Generate stories...). Right now it's all capabilities list, no "how do I actually use this?" (+5 points).

4. Inconsistent terminology - You switch between "user stories" and "stories," "generation" and "generator." Pick one and stick it (+2 points).

Quick Wins

• Restructure around workflows instead of script features → +6 points
• Add specific trigger terms to description → +4 points
• Number your workflow steps (epic → stories → sprint) → +5 points
• Include story and AC templates → +3 points

These four moves get you from 67 to ~85 without changing your core value.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.