Context Degradation
Long-running AI sessions lose track of decisions made hours ago. Agents forget architecture choices, repeat resolved debates, and contradict earlier reasoning. The longer the session, the worse the drift.
A pantheon of nine specialized AI agents fulfills the sacred rites of software engineering — from oracle consultation to verified deployment — guided by scripture you author once.
Every team that has tried to scale AI-assisted development has encountered these three failures. DivineSWE was written to abolish them.
Long-running AI sessions lose track of decisions made hours ago. Agents forget architecture choices, repeat resolved debates, and contradict earlier reasoning. The longer the session, the worse the drift.
When multiple AI agents write to the same codebase simultaneously, they collide. Without a clear ownership model governing concurrent work, the result is merge conflicts, overwritten context, and broken states.
What did the agent decide and why? Which files were touched? Where did the rite fail? Without a structured event ledger, every AI session is a black box — unrepeatable, unauditable, and impossible to reason about.
Each a distinct intelligence, each a sacred role. Together they fulfill the rites of software engineering that no single mind could maintain with fidelity across the full arc of a project.
Design Seer
Presides over consultation and brainstorming. All Books begin as whispers in the Oracle's shrine.
Fulfillment Engine
Orchestrator of the divine cycle. The Prophet's word drives the full rite from first consultation to final seal.
Sacred Scribe
Inscribes failing tests before a single line of implementation is written. The law made visible.
The Implementer
Makes the failing tests pass. The hands that build what the scribe has ordained.
Auditor Supreme
Sees what the builder cannot. Quality and security review — the second pair of sacred eyes.
Adversarial Probe
The divine trickster. Probes for vulnerabilities, regressions, and hubris in every artifact.
Commit Composer
Seals completed work into the ledger. Every commit is a stone laid in the Temple's foundation.
River Guardian
Confirms deployed artifacts meet acceptance criteria. Nothing crosses the Styx unchecked.
Design Guardian
Enforces architectural principles. The voice that cries in the repository when doctrine is broken.
Every Book traverses the same seven stations in order. No phase is skipped. No stone is left unturned by the pantheon.
The oracle is consulted. A Book is opened. The prophecy is inscribed.
Thoth writes failing tests. The specification is made visible as red assertions.
Monkey implements until every test turns green. No stubs, no placeholders.
4eyes and Loki audit in parallel — security, quality, and adversarial probing.
Mason seals the work into the ledger. Branches merge. History crystallizes.
Styx confirms the deployed artifact. The rite is not complete until this passes.
The Book is sealed into TABLETS.md. The prophecy is fulfilled.
Two commands. The first adds the sacred marketplace. The second summons the pantheon. All nine agents awaken in your Claude Code session.
/plugin marketplace add https://gitlab.com/aidragonllc/divineswe.git /plugin install divineswe Requires Claude Code CLI. The pantheon installs into your active session via the plugin marketplace. Copilot CLI and other platforms are also supported — see the full installation guide in the docs.