agile-scrum-mastery
Skill0 starsChanged 7 months agoMITView on GitHub
Run efficient Sprints, Standups, and Retrospectives, using Agile methodologies to improve the team's delivery pace and quality.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Negotiable: Leave room for discussion.
- Distinctive: line 30
Continuous Improvement: Every retrospective must yield at least one concrete process optimization action item.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agile & Scrum Mastery: Agile Delivery and Rhythm Management
Agile is not about being fast, but about getting feedback earlier.
Checklist
- Manage Backlog (Backlog Refinement) — Ensure User Stories satisfy the INVEST principles.
- Run Sprint Planning — Align goals, assess capacity, and determine the Sprint Backlog.
- Facilitate Daily Standups — Focus on blockers rather than simple status reporting.
- Execute Sprint Review & Retrospective — Demonstrate value and summarize process improvement items.
Core Framework: INVEST Principles
- Independent: Decoupled from other stories.
- Negotiable: Leave room for discussion.
- Valuable: Delivers value to users.
- Estimable: Effort can be assessed.
- Small: Atomic (can be completed within one Sprint).
- Testable: Can be verified.
Expert Principles
- Defend the Sprint Goal: During the Sprint, reject any non-urgent requirement injections.
- Monitor Velocity Trends: Focus on stability and consistency rather than just the absolute value.
- Continuous Improvement: Every retrospective must yield at least one concrete process optimization action item.
In this repository34 other files it gives its agents.
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.