When to use: The change touches >3 files or has unclear scope.
Flow
-
Plan
Use claude-best-practice. Write a plan for refactoring auth: scope, sequence, risks, rollback. Do not write code yet.✓ Copied
→ Plan document; no code
-
Critique
Critique your own plan as if you were the senior reviewer. What's missing?✓ Copied
→ Critique with concrete fixes
-
Execute
Now execute step 1 of the revised plan. Stop after that step.✓ Copied
→ Step 1 done; awaits sign-off
Outcome: Refactor that lands cleanly because it was thought through.
Pitfalls
- Plan too abstract — Insist on file-level granularity in the plan
When to use: Something went wrong and you have to write it up.
Flow
-
Gather
Use the postmortem template. Pull the timeline from /logs and recent commits.✓ Copied
→ Timeline auto-built
-
Five whys
Walk through five-whys on the root cause. Distinguish proximate from contributing.✓ Copied
→ Tiered causes
-
Action items
Generate action items with owners and due dates.✓ Copied
→ AI list owners flagged for review
Outcome: Postmortem doc that helps next time, not blame.
Pitfalls
- Auto-assigned owners are wrong — Always review owner assignments before publishing
When to use: Migration spans many files; you want to not miss steps.
Flow
-
Adopt
Apply the migration template to React 18→19. Customize for our codebase.✓ Copied
→ Tailored checklist
-
Track
Walk through the checklist, marking done/blocked for each item.✓ Copied
→ Progress log
Outcome: No 'we forgot to update X' surprises post-migration.
Pitfalls
- Checklist gets stale — Update for each major version; the skill provides the skeleton