vertical-slice-postmortem

Post-mortem analysis reviews root causes of defects in landed slices, improves source code and tests, and evaluates campaign resource spend to reduce future costs. This Skill automates root-cause analysis and generates retrospective reports for optimization.

Code slice optimization reviews major feature deliveries to improve code quality, reduce unnecessary token spend, and trim verification time. It hardens write-time recipes and tests to ensure future feature slices are delivered more efficiently.

Root-cause analysis on landed slices requires project-specific context and state to identify defect origins and improve the write-time recipes and tests that failed. The Skill automates this analysis and outputs a detailed retrospective report for review.

Yes, performing post-mortem improvements requires project-specific context and state to analyze defects and optimize code slices effectively. Without this context, the Skill cannot accurately evaluate resource spend or harden recipes.

The best way to reduce token spend is to analyze and trim unnecessary resource consumption during the post-delivery review phase. This Skill evaluates campaign resource spend and optimizes workflows to ensure the next feature slice is more efficient.

You should run a post-mortem review immediately after landing a new major feature slice. Running it at this stage allows you to analyze defects, improve failed recipes and tests, and optimize the workflow before starting the next delivery.