Skills-SIMarket
skills-si.com
Skill 제출
/
인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
생산성 및 협업 · 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

Jj4flmao / agent-skillsMIT

Skill 문서

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

More skills to explore

모든 Skills 보기

huashu-nuwa

huashu-nuwa

女娲造人：输入人名/主题/甚至只是模糊需求，自动深度调研→思维框架提炼→生成可运行的人物Skill。 两种入口：(1)明确人名→直接蒸馏 (2)模糊需求→诊断推荐→再蒸馏。 触发词：「造skill」「蒸馏XX」「女娲」「造人」「XX的思维方式」「做个XX视角」「更新XX的skill」。 模糊需求也触发：「我想提升决策质量」「有没有一种思维方式能帮我...」「我需要一个思维顾问」。 English triggers: "distill [person]", "nuwa", "create a [person] perspective skill", "how does [person] think", "I need a thinking advisor".

생산성 및 협업SKILL.md전체 ZIP
Aalchaincyf34.2K
저장한 Skills