Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generates agile sprint plans with capacity math, prioritized backlog, sprint goals, daily standup templates, and retro prompts to ensure focused delivery.
Generates agile sprint plans with capacity math, prioritized backlog, sprint goals, daily standup templates, and retro prompts to ensure focused delivery.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Plan, scope, and run agile sprints that actually ship. No ceremony bloat.
Takes your backlog (or a rough list of tasks) and produces a sprint plan with: Capacity math (team size ร available days ร focus factor) Story point allocation with buffer Sprint goal + success criteria Daily standup template Retro prompts tied to metrics
Tell your agent: "Plan a 2-week sprint for [team/project]" with: Team size and availability Backlog items (paste or describe them) Any hard deadlines or dependencies
Available hours = team_size ร sprint_days ร hours_per_day ร focus_factor focus_factor = 0.7 (accounts for meetings, interrupts, context switching)
Score each item: Reach: How many users/processes does this affect? (1-10) Impact: How much does it move the needle? (0.25, 0.5, 1, 2, 3) Confidence: How sure are you about estimates? (0.5, 0.8, 1.0) Effort: Person-days to complete RICE Score = (Reach ร Impact ร Confidence) / Effort Sort descending. Fill sprint capacity from top.
One sentence. Measurable. Example: "Ship user onboarding flow โ 80% of new signups complete setup within 48 hours."
Reserve 20% capacity for unplanned work. If you're filling 100% of capacity, you're already behind.
Every item needs: Code reviewed and merged Tests passing Deployed to staging Product owner sign-off
Each person posts: What I shipped yesterday What I'm shipping today What's blocking me (if anything) Skip "what I worked on" โ focus on shipped output.
Velocity: Planned points vs completed points Carry-over: What didn't get done and why? One thing to change: Pick ONE process improvement. Not five.
Sprint scope changed mid-sprint more than once No items completed until final 2 days Carry-over exceeds 30% of planned work Standup takes more than 10 minutes
Most sprint planning fails because teams skip capacity math and overcommit. This framework forces honest numbers first, then fills from a prioritized backlog. The 20% buffer isn't laziness โ it's how you actually hit your commitments. Built by AfrexAI โ AI context packs for business teams. Get the full SaaS Context Pack ($47) for sprint planning, roadmap templates, and 40+ agent-ready frameworks.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.