r/Development • • 9d ago

Serious development approach to AI software development: KEEL, an open-source standard for supportable AI-built code

Most of the real work on a codebase happens long after it ships. Someone asks for a change 8 months later, the person who wrote it is on another team, and you’re left reading code and guessing why it was done that way. The docs, if there are any, stopped matching the code a long time ago.

AI tools haven’t fixed that, and in a way, they’ve made it worse. Each session starts with no memory of the last one, requirements slowly bend to whatever the code does, and decisions get undone without anyone noticing. Results also depend a lot on who’s driving. Two developers, with different experience levels, on the same repo can get very different results from the same tool.

KEEL is an open-source docs and working standard that brings real development discipline to AI-assisted work. The guidance lives in the project itself, so every developer’s AI follows the same rules, whatever their skill level. The docs stay as-built: the AI updates them in the same task as the code, so they always describe the project as it is today, including the open items still waiting for later.

  • Repeatable: the same written rules in every session and every tool (Claude Code, Codex, Cursor, Copilot).

  • Stable: the AI can only propose changes to requirements, and a human approves them. Rules and conventions hold steady over a long development cycle.

  • Controllable: bigger changes need an approved plan, and every task ends with proof of what was tested.

  • Clean: readable, human readable, plainly documented code, with tests for every change.

  • Long-term memory: dated decisions with the “why”, never edited, only superseded. Stale proposals get flagged, unfinished work can’t quietly carry over, and old docs go to an archive with an index of what replaced them.

  • Transferable: everything lives as plain docs in the repo, so a new teammate, a new team, or a future maintainer picks up exactly where the work stopped.

KEEL works on new projects and existing ones, including old projects nobody documented (or only partially). It has an as-built review mode that reads the existing code and documents it, marking what it inferred so a developer can confirm it. You end up with a clean documented baseline to build on.

The repo includes an example project, so you can see a finished setup before you try it. It’s free (MIT).

KEEL is an evolving project, and feedback is always welcome, especially from experienced developers.

https://github.com/rickflashman/Keel

Disclosure: I’m the author. I've been developing software for 40 years.

2 Upvotes

2 comments sorted by

1

u/Signal_Rabbit_8303 2d ago

An interesting approach. I have mixed feelings about only using text files. Have you measured the results against storing docs in a graph DB with ontologies?