agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/retrospective-assistant/SKILL.md

retrospective

Skill4 starsChanged 30 days agoMITView on GitHub

[UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Not for: post-mortems for a production incident — use /incident; tracking metric trends between retros — use /metrics. Keywords: retrospective, retro, sprint review, lessons learned, action items.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dev-story, team-level and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    dev-story

    Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.

    Also in 12 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 12 projects that use this

  • CoralGameSkill

    team-narrative

    Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.

    Also in 12 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • +7 more from lilangMax
  • +1 more from CoralGame

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When /retrospective is invoked:

    line 136

“Common” is measured: kept by at least 6 in 10 of the 58 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Retrospective Assistant | 回顧助手

Language: English | 繁體中文

Guide structured team retrospectives to identify improvements and track action items. Support Sprint and Release retrospective types with multiple facilitation techniques.

引導結構化的團隊回顧，識別改善機會並追蹤行動項目。支援 Sprint 和 Release 回顧類型，提供多種引導技法。

Workflow | 工作流程

PREPARE ──► GATHER ──► ANALYZE ──► DECIDE ──► TRACK
  準備資料    蒐集意見    分析歸納    決定行動    追蹤落實

Phase 1: PREPARE | 準備

Gather data from git log, metrics, and issue tracker to ground the discussion.

從 git log、指標和 issue tracker 蒐集數據作為討論基礎。

Phase 2: GATHER | 蒐集

Collect perspectives using a structured technique.

使用結構化技法蒐集團隊觀點。

Phase 3: ANALYZE | 分析

Group items and identify patterns.

分組歸納並識別模式。

Phase 4: DECIDE | 決定

Select top 1-3 improvements as action items.

選出前 1-3 項改善作為行動項目。

Phase 5: TRACK | 追蹤

Review previous actions and track new ones.

檢視過去的行動項目並追蹤新項目。

Retrospective Types | 回顧類型

TypeWhenDurationFocus焦點
SprintEnd of iteration30-60 minProcess, collaboration, tools流程、協作、工具
ReleaseAfter release60-90 minQuality, metrics, cross-team品質、指標、跨團隊

Facilitation Techniques | 引導技法

TechniqueBest ForStructure結構
Start-Stop-ContinueQuick, defaultStart / Stop / Continue開始 / 停止 / 繼續
StarfishNuanced analysisMore / Keep / Less / Start / Stop更多 / 保持 / 減少 / 開始 / 停止
4LsTeam buildingLiked / Learned / Lacked / Longed for喜歡 / 學到 / 缺少 / 渴望
SailboatVisual, creativeWind / Anchor / Rocks / Island風 / 錨 / 礁石 / 島嶼

Commands | 指令

CommandAction說明
/retrospectiveInteractive Sprint retrospective (default)互動式 Sprint 回顧
/retrospective sprintSprint retrospectiveSprint 回顧
/retrospective releaseRelease retrospective with metricsRelease 回顧（含指標）
/retrospective actionsList open action items列出未完成行動項目
/retrospective --technique starfishUse specific technique使用指定技法

Action Item Format | 行動項目格式

FieldDescription說明
ActionSpecific description具體描述
OwnerSingle person responsible單一負責人
Due DateTarget completion預計完成日
StatusOpen → In Progress → Done狀態

Tracking Rules | 追蹤規則

  1. Review open actions at start of each retrospective | 每次回顧開始先檢視未完成項目
  2. Max 3 action items per retro | 每次回顧最多 3 項
  3. Stale items (2+ cycles) must be re-evaluated | 超過 2 個循環未完成須重新評估
  4. Each item has one owner | 每項須有單一負責人

Storage | 存放

docs/retrospectives/
├── RETRO-2026-03-15-sprint-12.md
├── RETRO-2026-03-26-release-v5.1.0.md
└── README.md    # Index (optional)

Integration | 與其他技能的整合

SkillIntegration整合方式
/metricsPull metrics data into release retrospective引用指標數據
/incidentPost-incident, suggest team retrospective事故後建議回顧
/adrIf architecture issues found, suggest ADR識別架構問題時建議 ADR
/commitCommit retro report with docs(retro):提交回顧報告

Next Steps Guidance | 下一步引導

After /retrospective completes:

Retrospective complete. Suggested next steps:

  • Commit the retrospective report: /commit
  • Create ADRs for architectural decisions identified: /adr
  • Track action items in your issue tracker
  • Schedule next retrospective

回顧完成。建議下一步：

  • 提交回顧報告：/commit
  • 為識別的架構決策建立 ADR：/adr
  • 在 issue tracker 中追蹤行動項目
  • 排定下次回顧

AI Agent Behavior | AI 代理行為

When /retrospective is invoked:

  1. Check type — Sprint (default) or Release
  2. Gather data — Scan git log, check docs/retrospectives/ for previous actions
  3. Guide technique — Use Start-Stop-Continue by default, or specified technique
  4. Generate report — Write to docs/retrospectives/RETRO-YYYY-MM-DD-[type].md
  5. Review past actions — Check previous retro for open action items
  6. Offer next steps — Show guidance above

When /retrospective actions is invoked:

  1. Scan docs/retrospectives/ for all retro files
  2. Parse action items from each
  3. Display open/in-progress items as table

Reference | 參考

  • Core Standard: retrospective-standards.md
  • Detailed Guide: guide.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free