Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

after-action-review

Estrellas1

Forks0

Actualizado24 de mayo de 2026, 16:31

This skill should be used when the user asks to review a completed team's process, run an after-action review, or evaluate team effectiveness. Use this skill when the user says "after action review", "AAR", "process review", "team retrospective", "review team process", "how did the team work", or at the prompt after a team completes its work. Distinct from `/evaluate-spawn` (output quality). AAR evaluates team process. Both can run in the same session.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

nthplusio

nthplusio/functional-claude

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

SKILL.md

readonly

name	after-action-review
description	This skill should be used when the user asks to review a completed team's process, run an after-action review, or evaluate team effectiveness. Use this skill when the user says "after action review", "AAR", "process review", "team retrospective", "review team process", "how did the team work", or at the prompt after a team completes its work. Distinct from `/evaluate-spawn` (output quality). AAR evaluates team process. Both can run in the same session.
version	0.26.0

After-Action Review (AAR)

Process evaluation for completed agent teams. Reviews team effectiveness using the military AAR format — 4 structured questions that surface what worked, what didn't, and specific improvements.

Prerequisites

A team must have completed its work (all tasks done or session ending)
Team config must still exist (run BEFORE TeamDelete)
Works with any team type

Protocol

Follow the AAR protocol at ${CLAUDE_PLUGIN_ROOT}/shared/aar-protocol.md.

The protocol covers:

Participant input — collect each teammate's perspective before synthesis (FM 7-0 participant-first principle)
4 core questions — plan vs reality, successes, improvements (synthesized from participant responses)
Usage summary — team composition, task completion, model assignments
Issue creation — offer gh issue create for plugin scope improvements; project scope noted in AAR only
Output — writes to docs/retrospectives/[team-name]-aar.md

Relationship to /evaluate-spawn

AAR evaluates process (team effectiveness); /evaluate-spawn evaluates output (spec quality prediction). See aar-protocol.md for full comparison.

Más de este repositorio

mismo repositorio

pm-branches

nthplusio/functional-claude

Use this skill when creating a git branch for a Linear or GitHub issue, writing a PR description, opening a pull request, or linking a PR to its tracked issue. Trigger phrases "create a branch", "new branch for this issue", "branch for

2026-06-091

pm-conventions

nthplusio/functional-claude

Use this skill when integrating, reading, or updating a project's conventions.md file — the document that captures house style for issue titles, labels, branch naming, PR descriptions, handoff phrasing, and review etiquette. Trigger phrases "set conventions", "load conventions", "where are the conventions", "what are our conventions", "add a convention", "edit conventions.md", "/pm-conventions", "the conventions say", "our team uses <X> format", "project conventions", "project title format". Also use proactively when another pm-* skill (pm-issues, pm-review, pm-improve, pm-branches, pm-handoff, pm-agent, pm-projects, pm-project-review) is about to write or evaluate text and a conventions file exists at `<repo>/.claude/pm/conventions.md` — the conventions must be loaded and applied before the skill writes anything user-facing.

2026-06-091

pm-dedup

nthplusio/functional-claude

Use this skill when the user asks to "find duplicate issues", "clean up duplicates", "what dupes are in the backlog", "/pm-dedup", or after a /pm-status briefing flags likely-dup clusters. Runs the `duplicates` lens against the team cache, has the agent judge each cluster, then offers merge / relate / close per cluster. Powered by the shared dedup engine in `hooks/lib/dedup.js`.

2026-06-091

pm-feedback

nthplusio/functional-claude

Use this skill when the user wants to report a bug, an unexpected result, or an improvement idea about the project-manager plugin ITSELF (or one of its pm-* skills) to the functional-claude maintainers — or when the agent has just hit a project-manager failure (a pm-* CLI error, a wrong/empty briefing, a crash, a clearly-incorrect result) and should offer to report it. Trigger phrases "report a bug in pm-review / pm-notes / any pm-* skill", "this plugin is broken", "pm gave the wrong answer", "send feedback about project-manager", "tell the functional-claude team", "/pm-feedback", "file a plugin issue". The defining cue is that the target of the complaint is the plugin or a named pm-* skill, not the user's own product. Assembles a README-shaped report (plugin + version, repro, expected vs actual, safe environment), scrubs every credential via the tested `hooks/lib/feedback-report.js` guard, previews it, then delivers — email to the Linear intake address (via resend-cli), GitHub issue fallback, or copy-paste d

2026-06-091

pm-handoff

nthplusio/functional-claude

Use this skill when the user wants to hand off work to another person or to the next stage of the lifecycle. Trigger phrases "hand this off to", "give this to", "I'm OOO", "passing this to", "covering for", "ready for release", "ready for QA", "ready for review", "release notes", "deploy handoff", "write a handoff", "/pm-handoff". Produces recipient-facing briefs with four required blocks (summary, what's done + how to use it, what's NOT done + next steps, open questions). Routes through configured channels (Linear, GitHub, markdown, chat/email).

2026-06-091

pm-improve

nthplusio/functional-claude

Distinct from `pm-review` (which *scores* whether an issue has the right structural shape), this skill *adds* project-specific context to an existing Linear or GitHub issue — relevant files, recent commits, owning modules, best-practice references, prior-art / related issues, and clarifying questions the author should answer before work starts. Use it when you want to give an issue more material to work from, not when you want to grade it. Trigger phrases "improve this issue", "enrich issue <ID>", "add context to this issue", "what's missing from this issue", "any relevant code for this issue", "research this issue", "qna this issue", "/pm-improve". Also use proactively after `pm-review` flags structural gaps that hint at missing context. Produces a draft enrichment; with `--apply`, posts it as a comment on the issue. Safe to re-run as repo state drifts — the marker mechanic replaces rather than stacks.

2026-06-091

name	after-action-review
description	This skill should be used when the user asks to review a completed team's process, run an after-action review, or evaluate team effectiveness. Use this skill when the user says "after action review", "AAR", "process review", "team retrospective", "review team process", "how did the team work", or at the prompt after a team completes its work. Distinct from `/evaluate-spawn` (output quality). AAR evaluates team process. Both can run in the same session.
version	0.26.0

After-Action Review (AAR)

Process evaluation for completed agent teams. Reviews team effectiveness using the military AAR format — 4 structured questions that surface what worked, what didn't, and specific improvements.

Prerequisites

A team must have completed its work (all tasks done or session ending)
Team config must still exist (run BEFORE TeamDelete)
Works with any team type

Protocol

Follow the AAR protocol at ${CLAUDE_PLUGIN_ROOT}/shared/aar-protocol.md.

The protocol covers:

Participant input — collect each teammate's perspective before synthesis (FM 7-0 participant-first principle)
4 core questions — plan vs reality, successes, improvements (synthesized from participant responses)
Usage summary — team composition, task completion, model assignments
Issue creation — offer gh issue create for plugin scope improvements; project scope noted in AAR only
Output — writes to docs/retrospectives/[team-name]-aar.md

Relationship to /evaluate-spawn

AAR evaluates process (team effectiveness); /evaluate-spawn evaluates output (spec quality prediction). See aar-protocol.md for full comparison.