The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Productivity · SKILL.md

agile-scrum-kanban

agile-scrum-kanban

Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: agile-scrum-kanban description: > Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags:

  • agile
  • scrum
  • kanban

Agile Scrum Kanban Skill

Purpose - comprehensive description

This skill manages and orchestrates Agile workflows and ceremonies.

Core Principles

  1. Iterative delivery over perfection
  2. Continuous feedback loop
  3. Transparent communication
  4. Sustainable pace
  5. Empowered teams

Agent Protocol

Triggers: Sprint start or end Input Context Required: Backlog items, team capacity Output Artifact: Sprint plan or retrospective report Response Formats:

{"status": "planned", "velocity": 45}

Decision Matrix

[Start] -> [Decide] -> [End]

Detailed Architectural Overview

[Architecture Diagram]
[Lifecycle Diagram]

Workflow Steps

Phase 1:

  1. Review backlog
  2. Estimate points
  3. Commit to sprint Phase 2:
  4. Daily standup
  5. Update kanban
  6. Unblock issues Phase 3:
  7. Mid-sprint check
  8. Adjust scope
  9. Communicate Phase 4:
  10. Sprint review
  11. Demo product
  12. Gather feedback Phase 5:
  13. Retrospective
  14. Action items
  15. Improve process Phase 6:
  16. Close sprint
  17. Update metrics
  18. Plan next sprint

Extended Troubleshooting Guide

SymptomPrimary CauseMitigation Action
Missed sprint goalPoor estimationRefine story points
Low velocityToo many blockersFocus on removing blockers
No communicationRemote disconnectEnforce daily async standups
Scope creepUndefined acceptanceClear acceptance criteria
BurnoutHigh workloadAdjust capacity planning
Technical debtIgnoring non-functionalAllocate 20% to tech debt

Complete Execution Scenario

Flow Diagram

Rules and Guidelines

  1. Always update Jira/Trello
  2. Never skip retrospectives
  3. Ensure accurate points
  4. Protect the sprint scope
  5. Celebrate wins

Reference Guides

Handoff

  • handoff to other skill

name: agile-scrum-kanban description: > Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags:

  • agile
  • scrum
  • kanban

Agile Scrum Kanban Skill

Purpose - comprehensive description

This skill manages and orchestrates Agile workflows and ceremonies.

Core Principles

  1. Iterative delivery over perfection
  2. Continuous feedback loop
  3. Transparent communication
  4. Sustainable pace
  5. Empowered teams

Agent Protocol

Triggers: Sprint start or end Input Context Required: Backlog items, team capacity Output Artifact: Sprint plan or retrospective report Response Formats:

{"status": "planned", "velocity": 45}

Decision Matrix

[Start] -> [Decide] -> [End]

Detailed Architectural Overview

[Architecture Diagram]
[Lifecycle Diagram]

Workflow Steps

Phase 1:

  1. Review backlog
  2. Estimate points
  3. Commit to sprint Phase 2:
  4. Daily standup
  5. Update kanban
  6. Unblock issues Phase 3:
  7. Mid-sprint check
  8. Adjust scope
  9. Communicate Phase 4:
  10. Sprint review
  11. Demo product
  12. Gather feedback Phase 5:
  13. Retrospective
  14. Action items
  15. Improve process Phase 6:
  16. Close sprint
  17. Update metrics
  18. Plan next sprint

Extended Troubleshooting Guide

SymptomPrimary CauseMitigation Action
Missed sprint goalPoor estimationRefine story points
Low velocityToo many blockersFocus on removing blockers
No communicationRemote disconnectEnforce daily async standups
Scope creepUndefined acceptanceClear acceptance criteria
BurnoutHigh workloadAdjust capacity planning
Technical debtIgnoring non-functionalAllocate 20% to tech debt

Complete Execution Scenario

Flow Diagram

Rules and Guidelines

  1. Always update Jira/Trello
  2. Never skip retrospectives
  3. Ensure accurate points
  4. Protect the sprint scope
  5. Celebrate wins

Reference Guides

Handoff

  • handoff to other skill

name: agile-scrum-kanban description: > Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags:

  • agile
  • scrum
  • kanban

Agile Scrum Kanban Skill

Purpose - comprehensive description

This skill manages and orchestrates Agile workflows and ceremonies.

Core Principles

  1. Iterative delivery over perfection
  2. Continuous feedback loop
  3. Transparent communication
  4. Sustainable pace
  5. Empowered teams

Agent Protocol

Triggers: Sprint start or end Input Context Required: Backlog items, team capacity Output Artifact: Sprint plan or retrospective report Response Formats:

{"status": "planned", "velocity": 45}

Decision Matrix

[Start] -> [Decide] -> [End]

Detailed Architectural Overview

[Architecture Diagram]
[Lifecycle Diagram]

Workflow Steps

Phase 1:

  1. Review backlog
  2. Estimate points
  3. Commit to sprint Phase 2:
  4. Daily standup
  5. Update kanban
  6. Unblock issues Phase 3:
  7. Mid-sprint check
  8. Adjust scope
  9. Communicate Phase 4:
  10. Sprint review
  11. Demo product
  12. Gather feedback Phase 5:
  13. Retrospective
  14. Action items
  15. Improve process Phase 6:
  16. Close sprint
  17. Update metrics
  18. Plan next sprint

Extended Troubleshooting Guide

SymptomPrimary CauseMitigation Action
Missed sprint goalPoor estimationRefine story points
Low velocityToo many blockersFocus on removing blockers
No communicationRemote disconnectEnforce daily async standups
Scope creepUndefined acceptanceClear acceptance criteria
BurnoutHigh workloadAdjust capacity planning
Technical debtIgnoring non-functionalAllocate 20% to tech debt

Complete Execution Scenario

Flow Diagram

Rules and Guidelines

  1. Always update Jira/Trello
  2. Never skip retrospectives
  3. Ensure accurate points
  4. Protect the sprint scope
  5. Celebrate wins

Reference Guides

Handoff

  • handoff to other skill

name: agile-scrum-kanban description: > Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags:

  • agile
  • scrum
  • kanban

Agile Scrum Kanban Skill

Purpose - comprehensive description

This skill manages and orchestrates Agile workflows and ceremonies.

Core Principles

  1. Iterative delivery over perfection
  2. Continuous feedback loop
  3. Transparent communication
  4. Sustainable pace
  5. Empowered teams

Agent Protocol

Triggers: Sprint start or end Input Context Required: Backlog items, team capacity Output Artifact: Sprint plan or retrospective report Response Formats:

{"status": "planned", "velocity": 45}

Decision Matrix

[Start] -> [Decide] -> [End]

Detailed Architectural Overview

[Architecture Diagram]
[Lifecycle Diagram]

Workflow Steps

Phase 1:

  1. Review backlog
  2. Estimate points
  3. Commit to sprint Phase 2:
  4. Daily standup
  5. Update kanban
  6. Unblock issues Phase 3:
  7. Mid-sprint check
  8. Adjust scope
  9. Communicate Phase 4:
  10. Sprint review
  11. Demo product
  12. Gather feedback Phase 5:
  13. Retrospective
  14. Action items
  15. Improve process Phase 6:
  16. Close sprint
  17. Update metrics
  18. Plan next sprint

Extended Troubleshooting Guide

SymptomPrimary CauseMitigation Action
Missed sprint goalPoor estimationRefine story points
Low velocityToo many blockersFocus on removing blockers
No communicationRemote disconnectEnforce daily async standups
Scope creepUndefined acceptanceClear acceptance criteria
BurnoutHigh workloadAdjust capacity planning
Technical debtIgnoring non-functionalAllocate 20% to tech debt

Complete Execution Scenario

Flow Diagram

Rules and Guidelines

  1. Always update Jira/Trello
  2. Never skip retrospectives
  3. Ensure accurate points
  4. Protect the sprint scope
  5. Celebrate wins

Reference Guides

Handoff

  • handoff to other skill

name: agile-scrum-kanban description: > Deep integration of Agile methodologies, Scrum frameworks, and Kanban boards. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags:

  • agile
  • scrum
  • kanban

Agile Scrum Kanban Skill

Purpose - comprehensive description

This skill manages and orchestrates Agile workflows and ceremonies.

Core Principles

  1. Iterative delivery over perfection
  2. Continuous feedback loop
  3. Transparent communication
  4. Sustainable pace
  5. Empowered teams

Agent Protocol

Triggers: Sprint start or end Input Context Required: Backlog items, team capacity Output Artifact: Sprint plan or retrospective report Response Formats:

{"status": "planned", "velocity": 45}

Decision Matrix

[Start] -> [Decide] -> [End]

Detailed Architectural Overview

[Architecture Diagram]
[Lifecycle Diagram]

Workflow Steps

Phase 1:

  1. Review backlog
  2. Estimate points
  3. Commit to sprint Phase 2:
  4. Daily standup
  5. Update kanban
  6. Unblock issues Phase 3:
  7. Mid-sprint check
  8. Adjust scope
  9. Communicate Phase 4:
  10. Sprint review
  11. Demo product
  12. Gather feedback Phase 5:
  13. Retrospective
  14. Action items
  15. Improve process Phase 6:
  16. Close sprint
  17. Update metrics
  18. Plan next sprint

Extended Troubleshooting Guide

SymptomPrimary CauseMitigation Action
Missed sprint goalPoor estimationRefine story points
Low velocityToo many blockersFocus on removing blockers
No communicationRemote disconnectEnforce daily async standups
Scope creepUndefined acceptanceClear acceptance criteria
BurnoutHigh workloadAdjust capacity planning
Technical debtIgnoring non-functionalAllocate 20% to tech debt

Complete Execution Scenario

Flow Diagram

Rules and Guidelines

  1. Always update Jira/Trello
  2. Never skip retrospectives
  3. Ensure accurate points
  4. Protect the sprint scope
  5. Celebrate wins

Reference Guides

Handoff

  • handoff to other skill
Saved skills