Writing & editingTechnical communicationtext
Write a humane letter to a future maintainer
Captures why a system is odd, not just how it works.

Ready to use
Prompt
From [SYSTEM NOTES] and [KNOWN INCIDENTS], write a one-page letter to the person maintaining this project next year. Explain the purpose, the surprising constraint, what broke before, the invariant that matters, and the quickest safe verification route. Separate confirmed history from team folklore. Give exact file or endpoint names only if present in the supplied material. End with three questions the next maintainer should ask before changing anything. Use a direct human tone, not a README outline or inspirational speech. Do not invent hidden architecture, credentials or promises of backward compatibility.