メニュー
Generate a sprint retrospective document from raw notes or observations. Returns what worked, what didn't, and 3 concrete action items with owners. Use when the user wants to run or document a sprint retro.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hamzafarooq/claude-code-starter --skill retro-facilitatorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Research emerging trends in a market or technology space. Returns signal vs noise breakdown with evidence. Use when the user asks what's changing in a market, what trends to watch, or what's coming next.
Turn any document, proposal, report, or outline into a stunning single-file HTML presentation using 34 pre-built professional templates. Use when the user wants to convert a markdown file, proposal, or written content into a beautiful visual HTML document ready to share or convert to PDF.
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
SOC 職業分類に基づく
SKILL.md を表示中
| name | retro-facilitator |
| description | Generate a sprint retrospective document from raw notes or observations. Returns what worked, what didn't, and 3 concrete action items with owners. Use when the user wants to run or document a sprint retro. |
Ask the user:
Then produce:
Sprint goal: [what you set out to do] Goal status: Achieved / Partially achieved / Missed — [one line on why]
4–6 bullets. Specific things that worked — behaviors, practices, or moments worth repeating. Not generic ("good communication") — concrete ("daily standups stayed under 10 minutes").
4–6 bullets. Be direct. Name the pattern, not just the symptom. Avoid blame — focus on systems and process.
Pick the one thing from "what didn't go well" that most impacted the sprint. One paragraph: what happened, why it happened, what it cost.
| Action | Owner | Done by |
|---|---|---|
| [specific change to make — not "improve communication"] | [name or role] | [next sprint / specific date] |
Limit to 3 action items. More than 3 means none will get done.
Any unresolved themes from previous retros. Flag if the same issue has appeared 3+ times.
End with: "At the next retro, start by reviewing these 3 action items."