Agent skill
post-mortem-learning
Analyze failures and suboptimal deliveries to identify root causes, contributing factors, and raw lessons. Activate after significant delivery failures, repeated QA failures, or when patterns of issues need to be understood.
Install this agent skill to your Project
npx add-skill https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/cross/post-mortem-learning
Metadata
Additional technical details for this skill
- id
- SKILL-POST-MORTEM-LEARNING-001
- track
- cross-cutting
- author
- gaai-framework
- status
- experimental
- version
- 1.0
- category
- cross
- updated at
- 1772064000
SKILL.md
Post-Mortem Learning
Purpose / When to Activate
Activate after:
- Significant delivery failures
- Repeated QA failures on the same area
- Delivery that missed its success metrics
- Patterns of issues that need systemic understanding
Process
- Reconstruct what happened end-to-end
- Compare expected vs actual outcomes
- Identify: technical causes, contextual gaps, decision errors, rule weaknesses
- Produce concrete failure narratives
- Extract raw lessons (non-generalized) — specific to this failure
Outputs
- Root cause analysis report
- Failure timeline
- Mapped rule gaps
- Raw lesson list (specific, not generic)
- Candidate improvement areas (for backlog or rules)
Quality Checks
- Root causes are specific, not generic ("insufficient testing" is invalid — "acceptance criterion #3 had no test coverage" is valid)
- Lessons are raw and specific, not platitudes
- Failure timeline is traceable
- Rule gaps link to specific rule files
Non-Goals
This skill must NOT:
- Propose solutions (produces inputs for backlog and rules, not fixes)
- Assign blame
- Generalize into vague lessons
Makes failures understandable and actionable. Enables serious continuous improvement.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ci-watch-and-fix
Watch GitHub Actions CI after PR creation, detect failures, extract logs, apply minimal fixes, and re-push — keeping the delivery session alive until CI resolves or escalating after 3 cycles. Activate immediately after gh pr create and before marking the story done.
qa-review
Validate that implemented code fully satisfies Story acceptance criteria, respects rules, and introduces no regressions. This is the hard quality gate — no pass means no delivery. Activate after implementation is complete.
compose-team
Assemble the context bundles for each sub-agent based on evaluate-story output. Produces spawn-ready packages for Planning, Implementation, QA, or MicroDelivery sub-agents. Activate after evaluate-story, before spawning any sub-agent.
coordinate-handoffs
Validate sub-agent handoff artefacts, sequence phase transitions, and manage retry and escalation logic. Activate after each sub-agent terminates to determine next action.
implement
Generate correct, minimal, maintainable code that satisfies a validated Story's acceptance criteria against an execution plan. Activate when a Story is validated, a plan exists, and all prerequisites are unambiguous.
delivery-high-level-plan
Transform validated Stories into a clear, minimal, governed execution plan. Used by the Planning Sub-Agent as the first planning pass before prepare-execution-plan for Tier 2/3, or as the sole planning output for simple Stories.
Didn't find tool you were looking for?