executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
agile-scrum-kanbanDeep integration of Agile methodologies, Scrum frameworks, and Kanban boards.
Independent GitHub snapshot · Automated classification · Original documentation governs
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:
This skill manages and orchestrates Agile workflows and ceremonies.
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}
[Start] -> [Decide] -> [End]
[Architecture Diagram]
[Lifecycle Diagram]
Phase 1:
| 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 |
Flow Diagram
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:
This skill manages and orchestrates Agile workflows and ceremonies.
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}
[Start] -> [Decide] -> [End]
[Architecture Diagram]
[Lifecycle Diagram]
Phase 1:
| 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 |
Flow Diagram
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:
This skill manages and orchestrates Agile workflows and ceremonies.
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}
[Start] -> [Decide] -> [End]
[Architecture Diagram]
[Lifecycle Diagram]
Phase 1:
| 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 |
Flow Diagram
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:
This skill manages and orchestrates Agile workflows and ceremonies.
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}
[Start] -> [Decide] -> [End]
[Architecture Diagram]
[Lifecycle Diagram]
Phase 1:
| 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 |
Flow Diagram
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:
This skill manages and orchestrates Agile workflows and ceremonies.
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}
[Start] -> [Decide] -> [End]
[Architecture Diagram]
[Lifecycle Diagram]
Phase 1:
| 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 |
Flow Diagram