skills.rest
leynos
leynosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

implementation-postmortem

Document architectural gaps and boundary violations in completed implementations.

2|1|Updated Jun 13, 2025
Search Tags:#architecture#tooling#reporting#postmortem#code-review#boundary-violation
One-click install
npx skills add https://github.com/leynos/agent-helper-scripts --skill implementation-postmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-postmortem
Source: https://github.com/leynos/agent-helper-scripts/tree/main/skills/implementation-postmortem
Command: npx skills add https://github.com/leynos/agent-helper-scripts --skill implementation-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Structured postmortems to surface design gaps, boundary violations, and tooling friction after code implementations or architectural efforts.

Core Features & Use Cases

  • Guidance for Phase 1 Context Gathering and Phase 2 Assessment
  • Phase-aligned templates (hexagonal, mvc, codec) to capture evidence
  • Actionable postmortem reports highlighting spec gaps and improvement opportunities

Quick Start

Review the PR or implementation and run Phase 1: Context Gathering to collect summaries, architecture context, and constraints.

Frequently Asked Questions about implementation-postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structured postmortem to uncover architecture gaps after a code implementation?▼

Run a structured postmortem by executing Phase 1 Context Gathering to collect summaries, architecture context, and constraints, then Phase 2 Assessment to surface boundary violations and tooling friction using formal templates.

What is an implementation postmortem and when should I perform one?▼

An implementation postmortem is a structured review applied during code reviews, architecture audits, PR retrospectives, or library evaluations to document architectural gaps and friction in completed implementations.

How do I document boundary violations found during an architecture audit?▼

Document boundary violations by collecting evidence across specification fidelity, boundary integrity, state management, and tooling effectiveness using phase-aligned templates like hexagonal, mvc, or codec during the assessment phase.

Do I need a specific postmortem framework to review specification fidelity and state management?▼

You need a formal postmortem framework aligned to the provided reference templates, which guide evidence collection across specification fidelity, boundary integrity, state management, and tooling effectiveness.

Can I use this structured postmortem approach for evaluating library and tooling effectiveness?▼

Yes, the structured postmortem process applies to library and tooling evaluations, surfacing tooling friction and improvement opportunities through context gathering and formal assessment phases.

What are the limitations of running postmortems without phase-aligned architecture templates?▼

Without phase-aligned templates, postmortems lack structured evidence capture across architecture dimensions, making it difficult to systematically surface spec gaps and boundary violations in the final report.

Related Skills

Explore More Software Engineering Skills→
AGMO-IncAGMO-Inc
4

save-impl

Archive implementation summaries to an Obsidian vault with linked plan references.

Official
Advanced
yxc023yxc023

agent-native-audit

Evaluate agent-native architectures across codebases and generate scored audit reports.

Community
Advanced
Open-Earth-FoundationOpen-Earth-Foundation
45

repo-doc-audit

Audit repository documentation for inconsistencies and generate a prioritized fix report.

Official
Basic
wade56754wade56754

ai-ad-code-verifier

Verify ad-code integration for cross-module boundary and API violations.

Community
Advanced