Every time I started a new feature, I went through the same routine. Open a blank doc. Try to remember what sections a proper technical spec needs. Copy an old ADR template from a previous project and strip out the parts that don't apply. Realize halfway through that I forgot to think about rollback steps, or access control, or what happens when the thing fails at 3 AM.
None of this is hard work. It is just repetitive, and repetitive work is exactly the kind of thing that gets skipped when you are in a hurry. And skipping it is how you end up shipping a feature with no threat model, no rollback plan, and no one on the team quite sure why a decision was made six months later.
So I built engineering-docs. It is a set of 21 skills for coding agents that cover the full lifecycle of writing software, from the first fuzzy idea to the postmortem after something breaks in production.
The actual problem I was solving
I work across a few different projects at once, things like OwnPay, a self-hosted payment gateway, and a couple of security tools. Every one of them needs the same kind of documentation. A spec before you build. An architecture doc once the shape of the system is clear. A threat model before anything touches money or user data. A deployment plan before you push to production. A postmortem when something goes wrong, because something always eventually goes wrong.
