ultimate-project, combining spec discipline and engineering memory, no vectordb

Lately, everyone has been sharing SKILL.md and AGENT.md files.

I think the more important layer is actually SPEC and MEMORY.

That is the idea behind this repo:

Ultimate Project combines two separate disciplines:

Beastmode -> the software engineering discipline

spec-kit -> the structure and organization of specs

Beastmode gives the engineering workflow. spec-kit gives the project a clear spec foundation.

Putting them together creates a development loop where the system starts from specs, keeps context in memory, and follows a more structured implementation lifecycle.

Combination Repo: https://github.com/senolcolak/ultimate-project

beastmode: https://github.com/BugRoger/beastmode spec-kit: https://github.com/github/spec-kit

For small project, a simple history file ./store-my-history in a dir works. For bigger projects, I think structured specs + engineering memory matter much more than prompt files alone.

I’d be curious how others here are handling spec organization, memory, and iteration flow in agent-driven development.