phuryn/pm-skills

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill retro

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions

  1. Choose a retro format based on context (or let the user pick):

Format A — Start / Stop / Continue:

  • Start: What should we begin doing?
  • Stop: What should we stop doing?
  • Continue: What's working well that we should keep?

Format B — 4Ls (Liked / Learned / Lacked / Longed For):

  • Liked: What did the team enjoy?
  • Learned: What new knowledge was gained?
  • Lacked: What was missing?
  • Longed For: What do we wish we had?

Format C — Sailboat:

  • Wind (propels us): What's driving us forward?
  • Anchor (holds us back): What's slowing us down?
  • Rocks (risks): What dangers lie ahead?
  • Island (goal): Where are we trying to get to?
  1. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
  • Group similar items into themes
  • Identify the most frequently mentioned topics
  • Note sentiment patterns (frustration, energy, confusion)
  1. Analyze the sprint performance:
  • Sprint goal: achieved or not?
  • Velocity vs. commitment (over-committed? under-committed?)
  • Blockers encountered and how they were resolved
  • Collaboration patterns (what worked, what didn't)
  1. Generate prioritized action items:
PriorityAction ItemOwnerDeadlineSuccess Metric
1[Specific, actionable improvement][Name/Role][Date][How we'll know it worked]
  • Limit to 2-3 action items (more won't get done)
  • Each must be specific, assignable, and measurable
  • Reference previous retro actions if available — were they completed?
  1. Create the retro summary:
   ## Sprint [X] Retrospective — [Date]

   ### Sprint Performance
   - Goal: [Achieved / Partially / Missed]
   - Committed: [X pts] | Completed: [Y pts]

   ### Key Themes
   1. [Theme] — [summary]

   ### Action Items
   1. [Action] — [Owner] — [By date]

   ### Carry-over from Last Retro
   - [Previous action] — [Status: Done / In Progress / Not Started]

Save as markdown. Keep the tone constructive — the goal is improvement, not blame.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1時間の導入数
4
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日