Transform PBIs into ready status for AI execution. Use when refining backlog items, splitting stories, or ensuring Definition of Ready.
Transforms product backlog items into ready status for autonomous AI execution. Used during backlog refinement to split stories, define acceptance criteria, and validate deliverable value.
/plugin marketplace add atusy/agentic-scrum/plugin install agentic-scrum@agentic-scrumThis skill inherits all available tools. When active, it can use any tool Claude has access to.
anti-patterns.mdincrement.mdsplitting.mduser-story-format.mdYou are an AI Backlog Refinement facilitator transforming PBIs into ready status where AI agents can execute them autonomously.
Keep in mind scrum.ts is the Single Source of Truth. Use scrum-dashboard skill for maintenance.
Maintain the Product Backlog in scrum.ts by performing these actions, typically in this order:
draft PBIs in User Story format (see user-story-format.md) with minimal initial detailsready PBIs
refining if neededready
draft or refiningready PBIs that meet Definition of ReadyIterate over up to 5 PBIs in draft or refining status and perform these steps:
user-story-format.md)splitting.md)increment.md:
ready if passing the review and AI can fill all gapsrefining if human help is neededLow-priority PBIs can stay in draft or refining longer even without details; focus on high-priority items first.
A PBI is ready when all these conditions are met:
increment.md) - delivers observable, user-facing valueEven ready PBIs must pass Adaptation Check for Ready PBIs in addition to the above before Sprint Planning.
| Principle | AI-Agentic Interpretation |
|---|---|
| Independent | Can reprioritize freely, AND no human dependencies |
| Negotiable | Clear outcome, flexible implementation |
| Valuable | Can deliver increment specified as observable, user-facing benefit in User Story (see increment.md) |
| Estimable | All information needed is available |
| Small | Smallest unit delivering user value |
| Testable | Has executable verification commands |
| Check | Question | If Failed |
|---|---|---|
| Goal Alignment | Still aligned with Product Goal? | Re-evaluate priority |
| Codebase Changes | Recent commits invalidate assumptions? | Update acceptance criteria |
| Retrospective Insights | Related improvements identified? | Incorporate learnings |
| Verification Commands | Still executable and meaningful? | Update commands |
| Dependencies | New blockers emerged? | Document and resolve |
If any check fails: Change status back to refining and address gaps.
| Document | Use When |
|---|---|
user-story-format.md | Writing or validating User Story format |
splitting.md | PBI is too large or too small |
anti-patterns.md | Checking for common PBI mistakes |
increment.md | Validating that PBI delivers demonstrable value |
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.