fde-closelisted

# @fde-close ## Token efficiency Load `context.md`, `reality.md`, `success.md`, `delivery.md`, and `decisions.md`. This skill needs the full picture -- it is the only one that does. Do not load `terrain.md` unless the handoff document requires codebase-specific guidance. ## Purpose The engagement doesn't end at ship. It ends when the customer team can maintain what was built without calling you. This skill captures everything learned, encodes reusable patterns, and leaves the customer genuinely self-sufficient. ## Opening Handoff isn't a doc dump — it's "what will bite them when you're gone?" Ask that in plain language; their answer shapes everything you write. ## Three things to produce **1. The retrospective.** What went well, what was harder than expected, what would you do differently. Blame-free. Specific. Useful for the next engagement. Key questions to work through: - Did the real problem match the brief? - Were there trust moments that mattered? - What did we learn about the codebase that wasn't in `terrain.md`? - What risk almost became a real problem? - If AI components were built or integrated: did they behave as expected in production? What failure modes appeared that the prototype did not reveal? Is the team equipped to maintain them? **2. The pattern.** If something happened in this engagement that will happen again, a compliance approach, a migration pattern, a stakeholder dynamic, encode it. Write it as a skill or a note others can use. "If you do it