agile/SKILL.md
Sprint-based agile development with parallel agent execution. Use when the user wants to run an agile sprint, plan sprint work, conduct standups, run retrospectives, manage a backlog, estimate story points, track velocity, or coordinate parallel development across multiple agents acting as Scrum team roles (Scrum Master, Product Owner, Tech Lead, Frontend Dev, Backend Dev, QA Engineer). Also use when the user mentions sprints, user stories, acceptance criteria, definition of done, kanban, or SAFe. Triggers on: 'run a sprint', 'sprint planning', 'standup', 'retrospective', 'backlog grooming', 'agile workflow', 'scrum team'.
npx skillsauth add jswortz/my-skills agileInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Coordinate parallel development using Gemini CLI agents as a Scrum team.
| Ceremony | Agent | Command | |----------|-------|---------| | Sprint Planning | scrum-master | Plan sprint scope, create tasks | | Daily Standup | scrum-master | Collect status from all agents | | Development | frontend-dev, backend-dev | Parallel feature implementation | | Code Review | tech-lead | Architecture review, standards | | Testing | qa-engineer | Acceptance tests, regression | | Sprint Review | product-owner | Validate acceptance criteria | | Retrospective | scrum-master | What went well/improve/actions |
Launch the scrum-master agent to initialize the sprint:
Task(subagent_type="scrum-master", prompt="Plan sprint N: [goal]. Break down these user stories into tasks, estimate story points, and create the sprint backlog using TaskCreate.")
The scrum-master will:
Launch development agents in parallel for independent stories:
Task(subagent_type="frontend-dev", prompt="Implement [story]: [details]")
Task(subagent_type="backend-dev", prompt="Implement [story]: [details]")
Task(subagent_type="qa-engineer", prompt="Write acceptance tests for [story]")
Task(subagent_type="tech-lead", prompt="Review implementation of [story] for architecture, code quality, and standards compliance")
Task(subagent_type="product-owner", prompt="Validate [story] against acceptance criteria: [criteria]")
Task(subagent_type="scrum-master", prompt="Run sprint N retrospective. Review completed tasks, velocity, blockers encountered, and generate action items for next sprint.")
| Agent | Role | Focus |
|-------|------|-------|
| scrum-master | Facilitator | Ceremonies, impediments, process |
| product-owner | Value owner | Backlog, acceptance criteria, priorities |
| tech-lead | Architecture | Design decisions, code review, standards |
| frontend-dev | UI developer | Frontend implementation |
| backend-dev | API developer | Backend implementation, data layer |
| qa-engineer | Quality | Testing, validation, bug tracking |
Use the knowledge graph to persist sprint metrics:
mcp__memory__create_entities([{
name: "Sprint N",
entityType: "sprint",
observations: [
"Planned points: 40",
"Completed points: 35",
"Velocity: 35",
"Goal: [sprint goal]",
"Status: completed"
]
}])
Query historical velocity:
mcp__memory__search_nodes("sprint velocity")
For continuous flow instead of sprints:
product-owner to maintain a prioritized backlogscrum-master as flow master to monitor cycle timeFor multi-team coordination, see references/safe.md.
If the mcp-atlassian MCP server is configured, agents can:
See references/jira-integration.md for setup.
research
Constant-Time Analyzer (ct-analyzer)
testing
--- name: condition-based-waiting description: -- name: Condition-Based Waiting description: Replace arbitrary timeouts with condition polling for reliable async tests when_to_use: when tests have ... --- -- name: Condition-Based Waiting description: Replace arbitrary timeouts with condition polling for reliable async tests when_to_use: when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior version: 1.1.0 languages: all --- # Condition-Based Waiting ## Overvi
testing
--- name: collision-zone-thinking description: -- name: Collision-Zone Thinking description: Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?" when_... --- -- name: Collision-Zone Thinking description: Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?" when_to_use: when conventional approaches feel inadequate and you need breakthrough innovation by forcing unrelated concepts together version: 1.1.0
documentation
--- name: canvas-design description: -- name: canvas-design description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the... --- -- name: canvas-design description: 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