# Agile Scrum Kanban

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

- Skill: `j4flmao/agile-scrum-kanban` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add j4flmao/agile-scrum-kanban`
- Raw SKILL.md: https://api.skillmd.com/api/skills/j4flmao/agile-scrum-kanban/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- License: MIT
- Author: j4flmao (https://skillmd.com/u/j4flmao)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/j4flmao/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:
```json
{"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:
1. Daily standup
2. Update kanban
3. Unblock issues
Phase 3:
1. Mid-sprint check
2. Adjust scope
3. Communicate
Phase 4:
1. Sprint review
2. Demo product
3. Gather feedback
Phase 5:
1. Retrospective
2. Action items
3. Improve process
Phase 6:
1. Close sprint
2. Update metrics
3. Plan next sprint

## Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Missed sprint goal | Poor estimation | Refine story points |
| Low velocity | Too many blockers | Focus on removing blockers |
| No communication | Remote disconnect | Enforce daily async standups |
| Scope creep | Undefined acceptance | Clear acceptance criteria |
| Burnout | High workload | Adjust capacity planning |
| Technical debt | Ignoring non-functional | Allocate 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
- [Ref 1](references/ref_1.md)
- [Ref 2](references/ref_2.md)
- [Ref 3](references/ref_3.md)
- [Ref 4](references/ref_4.md)
- [Ref 5](references/ref_5.md)
- [Ref 6](references/ref_6.md)
- [Ref 7](references/ref_7.md)
- [Ref 8](references/ref_8.md)

## Handoff
- handoff to other skill
<!-- compression footer -->

---
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:
```json
{"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:
1. Daily standup
2. Update kanban
3. Unblock issues
Phase 3:
1. Mid-sprint check
2. Adjust scope
3. Communicate
Phase 4:
1. Sprint review
2. Demo product
3. Gather feedback
Phase 5:
1. Retrospective
2. Action items
3. Improve process
Phase 6:
1. Close sprint
2. Update metrics
3. Plan next sprint

## Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Missed sprint goal | Poor estimation | Refine story points |
| Low velocity | Too many blockers | Focus on removing blockers |
| No communication | Remote disconnect | Enforce daily async standups |
| Scope creep | Undefined acceptance | Clear acceptance criteria |
| Burnout | High workload | Adjust capacity planning |
| Technical debt | Ignoring non-functional | Allocate 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
- [Ref 1](references/ref_1.md)
- [Ref 2](references/ref_2.md)
- [Ref 3](references/ref_3.md)
- [Ref 4](references/ref_4.md)
- [Ref 5](references/ref_5.md)
- [Ref 6](references/ref_6.md)
- [Ref 7](references/ref_7.md)
- [Ref 8](references/ref_8.md)

## Handoff
- handoff to other skill
<!-- compression footer -->

---
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:
```json
{"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:
1. Daily standup
2. Update kanban
3. Unblock issues
Phase 3:
1. Mid-sprint check
2. Adjust scope
3. Communicate
Phase 4:
1. Sprint review
2. Demo product
3. Gather feedback
Phase 5:
1. Retrospective
2. Action items
3. Improve process
Phase 6:
1. Close sprint
2. Update metrics
3. Plan next sprint

## Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Missed sprint goal | Poor estimation | Refine story points |
| Low velocity | Too many blockers | Focus on removing blockers |
| No communication | Remote disconnect | Enforce daily async standups |
| Scope creep | Undefined acceptance | Clear acceptance criteria |
| Burnout | High workload | Adjust capacity planning |
| Technical debt | Ignoring non-functional | Allocate 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
- [Ref 1](references/ref_1.md)
- [Ref 2](references/ref_2.md)
- [Ref 3](references/ref_3.md)
- [Ref 4](references/ref_4.md)
- [Ref 5](references/ref_5.md)
- [Ref 6](references/ref_6.md)
- [Ref 7](references/ref_7.md)
- [Ref 8](references/ref_8.md)

## Handoff
- handoff to other skill
<!-- compression footer -->

---
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:
```json
{"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:
1. Daily standup
2. Update kanban
3. Unblock issues
Phase 3:
1. Mid-sprint check
2. Adjust scope
3. Communicate
Phase 4:
1. Sprint review
2. Demo product
3. Gather feedback
Phase 5:
1. Retrospective
2. Action items
3. Improve process
Phase 6:
1. Close sprint
2. Update metrics
3. Plan next sprint

## Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Missed sprint goal | Poor estimation | Refine story points |
| Low velocity | Too many blockers | Focus on removing blockers |
| No communication | Remote disconnect | Enforce daily async standups |
| Scope creep | Undefined acceptance | Clear acceptance criteria |
| Burnout | High workload | Adjust capacity planning |
| Technical debt | Ignoring non-functional | Allocate 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
- [Ref 1](references/ref_1.md)
- [Ref 2](references/ref_2.md)
- [Ref 3](references/ref_3.md)
- [Ref 4](references/ref_4.md)
- [Ref 5](references/ref_5.md)
- [Ref 6](references/ref_6.md)
- [Ref 7](references/ref_7.md)
- [Ref 8](references/ref_8.md)

## Handoff
- handoff to other skill
<!-- compression footer -->

---
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:
```json
{"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:
1. Daily standup
2. Update kanban
3. Unblock issues
Phase 3:
1. Mid-sprint check
2. Adjust scope
3. Communicate
Phase 4:
1. Sprint review
2. Demo product
3. Gather feedback
Phase 5:
1. Retrospective
2. Action items
3. Improve process
Phase 6:
1. Close sprint
2. Update metrics
3. Plan next sprint

## Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Missed sprint goal | Poor estimation | Refine story points |
| Low velocity | Too many blockers | Focus on removing blockers |
| No communication | Remote disconnect | Enforce daily async standups |
| Scope creep | Undefined acceptance | Clear acceptance criteria |
| Burnout | High workload | Adjust capacity planning |
| Technical debt | Ignoring non-functional | Allocate 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
- [Ref 1](references/ref_1.md)
- [Ref 2](references/ref_2.md)
- [Ref 3](references/ref_3.md)
- [Ref 4](references/ref_4.md)
- [Ref 5](references/ref_5.md)
- [Ref 6](references/ref_6.md)
- [Ref 7](references/ref_7.md)
- [Ref 8](references/ref_8.md)

## Handoff
- handoff to other skill
<!-- compression footer -->