agentleFS
Sign inStart free
phoenixvnphoenixvn/claude-code-agency/.claude/skills/retro/SKILL.md

retro

Skill0 starsChanged 7 months agoMITView on GitHub

Review what worked and what didn't. Extract lessons for the next sprint. "What went well this sprint?" - Deliverable quality was high - Good communication and feedback loops - On-time delivery - Effective multi-agent coordination - Other (free text) "What didn't go well?" - Missed deadlines - Too many revision rounds - Scope creep - Unclear requirements - Other (free text) "What should we change for next sprint?" - Smaller tasks / better estimation - More frequent reviews - Better…

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-tune, ios-clean 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.
  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 9 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • +1 more from Saqlain-811
  • +2 more from ShreyRavi

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the completed sprint plan and any deliverables produced during the sprint.

    line 8
  2. Distinctive:

    Use AskUserQuestion (multiSelect where appropriate):

    line 18
  3. Very specific:

    Use template from .claude/docs/templates/retrospective.md.

    line 42
  4. Very specific:

    Update active.md. Offer to run /sprint-plan for the next sprint.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 171 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

/retro — Sprint Retrospective

Review what worked and what didn't. Extract lessons for the next sprint.

Instructions

Phase 1: Sprint Data

Read the completed sprint plan and any deliverables produced during the sprint.

Phase 2: Analysis

Spawn project-lead to analyze:

  • Tasks completed vs planned (completion rate)
  • Quality of deliverables (any revisions needed?)
  • Timeline accuracy (delivered on time?)
  • Any scope changes during the sprint

Phase 3: Guided Discussion

Use AskUserQuestion (multiSelect where appropriate):

"What went well this sprint?"

  • Deliverable quality was high
  • Good communication and feedback loops
  • On-time delivery
  • Effective multi-agent coordination
  • Other (free text)

"What didn't go well?"

  • Missed deadlines
  • Too many revision rounds
  • Scope creep
  • Unclear requirements
  • Other (free text)

"What should we change for next sprint?"

  • Smaller tasks / better estimation
  • More frequent reviews
  • Better requirement clarity upfront
  • Different team composition
  • Other (free text)

Phase 4: Write Retrospective

Use template from .claude/docs/templates/retrospective.md. Save to production/sprints/retro-sprint-[N].md.

Phase 5: Action Items

Extract concrete action items for the next sprint. Update active.md. Offer to run /sprint-plan for the next sprint.

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