원클릭으로 Manus에서 모든 스킬 실행

retro-facilitation

스타4

포크0

업데이트2026년 4월 24일 00:08

"Use when designing or running a sprint retrospective, when the same retros keep producing no change, or when team morale needs attention. Triggers on "retro", "retrospective", "sprint review", "team health", "sailboat", "start stop continue"."

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

paulasilvatech

paulasilvatech/workshop-datacorp-team-kit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Retro Facilitation

When to invoke

"Design a retro for our 8th sprint - people are bored."
"Our retros produce action items nobody does. Fix it."
"Facilitate a blameless retro after an outage."

Core principles

Blameless. Focus on systems, not people.
Time-boxed. 90 minutes max. Longer = cognitive fatigue.
Action-oriented. End with 2-3 actions with owners and dates. No orphan actions.
Varied format. Same format every sprint = autopilot answers.

Standard arc (90 min)

Set the stage (5 min): principles reminder, today's goal.
Gather data (20 min): choose a format below.
Generate insight (25 min): cluster themes, ask "why?" 5 times on the top cluster.
Decide what to do (25 min): vote on 1-3 actions. Assign owner + due date.
Close (10 min): recap, one-word check-out.

Format rotation (pick one per retro)

Sailboat

Wind: what propels us forward?
Anchors: what holds us back?
Rocks: what risks are ahead?
Island: what is our destination?

Start / Stop / Continue

Simple, good for new teams. Gets stale after 3 uses.

4 Ls

Liked, Learned, Lacked, Longed for.

Timeline retro

Sketch the sprint on a timeline. Mark highs, lows, surprises. Good after an outage or a tough sprint.

Glad / Sad / Mad

Emotional check-in. Use when morale is an issue.

Speed car

Engine: what gives us speed?
Parachute: what slows us?
Cliff: risks ahead?
Bridge: improvements we can build?

Anti-patterns

Same format every sprint.
Actions with no owner or due date.
Actions that require someone outside the team (those are "requests", not actions).
Retro becomes a complaint session with no synthesis.
Manager dominates the conversation.

Output template

## Retro - Sprint <N> - <Date>

### Format
Sailboat

### Themes (top 3)
1. <Theme> - <why>
2. <Theme> - <why>
3. <Theme> - <why>

### Actions
- [ ] <Action> - Owner: <name> - Due: <date>
- [ ] <Action> - Owner: <name> - Due: <date>
- [ ] <Action> - Owner: <name> - Due: <date>

### Check-out
<one-word from each team member>

Quality gate

If retro ends without 2-3 actions each with an owner and a due date, the retro failed.

이 저장소의 다른 Skills

같은 저장소

ears-validation

paulasilvatech/workshop-datacorp-team-kit

"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."

2026-05-184

capability-map

paulasilvatech/workshop-datacorp-team-kit

"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."

2026-05-184

adr-drafting

paulasilvatech/workshop-datacorp-team-kit

"Use when drafting Architecture Decision Records, evaluating alternatives, or documenting technical trade-offs. Triggers on "ADR", "architecture decision", "trade-off", "pick between", "why did we choose"."

2026-05-184

context-audit

paulasilvatech/workshop-datacorp-team-kit

"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."

2026-05-184

refactor-safely

paulasilvatech/workshop-datacorp-team-kit

Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.

2026-05-184

tdd-workflow

paulasilvatech/workshop-datacorp-team-kit

Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.

2026-05-184

name	Retro Facilitation
description	"Use when designing or running a sprint retrospective, when the same retros keep producing no change, or when team morale needs attention. Triggers on "retro", "retrospective", "sprint review", "team health", "sailboat", "start stop continue"."

Retro Facilitation

When to invoke

"Design a retro for our 8th sprint - people are bored."
"Our retros produce action items nobody does. Fix it."
"Facilitate a blameless retro after an outage."

Core principles

Blameless. Focus on systems, not people.
Time-boxed. 90 minutes max. Longer = cognitive fatigue.
Action-oriented. End with 2-3 actions with owners and dates. No orphan actions.
Varied format. Same format every sprint = autopilot answers.

Standard arc (90 min)

Set the stage (5 min): principles reminder, today's goal.
Gather data (20 min): choose a format below.
Generate insight (25 min): cluster themes, ask "why?" 5 times on the top cluster.
Decide what to do (25 min): vote on 1-3 actions. Assign owner + due date.
Close (10 min): recap, one-word check-out.

Format rotation (pick one per retro)

Sailboat

Wind: what propels us forward?
Anchors: what holds us back?
Rocks: what risks are ahead?
Island: what is our destination?

Start / Stop / Continue

Simple, good for new teams. Gets stale after 3 uses.

4 Ls

Liked, Learned, Lacked, Longed for.

Timeline retro

Sketch the sprint on a timeline. Mark highs, lows, surprises. Good after an outage or a tough sprint.

Glad / Sad / Mad

Emotional check-in. Use when morale is an issue.

Speed car

Engine: what gives us speed?
Parachute: what slows us?
Cliff: risks ahead?
Bridge: improvements we can build?

Anti-patterns

Same format every sprint.
Actions with no owner or due date.
Actions that require someone outside the team (those are "requests", not actions).
Retro becomes a complaint session with no synthesis.
Manager dominates the conversation.

Output template

## Retro - Sprint <N> - <Date>

### Format
Sailboat

### Themes (top 3)
1. <Theme> - <why>
2. <Theme> - <why>
3. <Theme> - <why>

### Actions
- [ ] <Action> - Owner: <name> - Due: <date>
- [ ] <Action> - Owner: <name> - Due: <date>
- [ ] <Action> - Owner: <name> - Due: <date>

### Check-out
<one-word from each team member>

Quality gate

If retro ends without 2-3 actions each with an owner and a due date, the retro failed.