╱│╲
╭──────────────╮
╱ ◉ ◉ ╲
│ ──────── │
╲ ╱
╰──────┬─────────╯
═════════════╪═════════════
║
T H E L O R D
The Lord is not a tool. He is the discipline of software development made manifest — what every codebase becomes when every developer who touched it wrote the spec first, captured what they learned, and never let knowledge die with the session.
Spec-driven development. Growing knowledge base. One plugin, one identity, one way to work.
Every developer who uses an AI coding assistant eventually hits the same wall.
The assistant forgets. Every session starts from zero — no memory of the decisions made last week, the pattern that took three hours to figure out, the reason that architectural choice was made. You explain the context again. And again.
The other wall: code that runs but shouldn't. Features built without a spec, where "done" means it works today but nobody knows what it's supposed to do. The spec lived in someone's head. Now it's gone.
codelord closes both gaps. Vault for memory. Specs for discipline. Together, they make every session build on the last.
codelord runs on three pillars:
Vault — a personal git repository that grows with you. Every generalizable pattern, architectural decision, and hard-won insight lives here as an atomic note. The vault persists across sessions, across projects, across time. What you learn once, you keep forever.
Specs — a contract between intention and execution. Before any feature is built, a spec exists in eidos/ describing what it should do — not how. The Lord never touches code without one. When spec and code diverge, codelord surfaces it.
Context loading — at the start of every session, codelord loads only what the current task needs: the project map, the relevant spec, the directly applicable vault notes. Nothing more. Context is finite. Every token counts.
The loop: start with /codelord:vault → spec with /codelord:spec → build → end with /codelord:done. Each session closes the gap between what you know and what the code reflects.
claude plugin install https://github.com/yuribodo/codelord/codelord:setup
The setup wizard will:
- Ask about your tech stack and preferences
- Create your personal vault repository
- Configure the plugin with your vault path
- Explain the three daily habits
| Step | Command | When |
|---|---|---|
| Start | /codelord:vault |
Every session — loads project context |
| Spec | /codelord:spec |
Before any implementation — ensures you have a spec |
| Code | — | Implement against the spec |
| Capture | /codelord:remember |
When you find a generalizable pattern |
| End | /codelord:done |
End of session — persists what was learned |
| Skill | Description |
|---|---|
/codelord:setup |
First-time onboarding wizard — creates your vault and configures the plugin |
/codelord:vault |
80/20 context loader — loads project map and directly relevant notes |
/codelord:spec |
Spec-driven dev wizard — creates or updates a spec for the current feature |
/codelord:remember |
Knowledge capture — promotes a generalizable pattern to your vault |
/codelord:done |
Session close — writes session log and updates vault state |
| Skill | Description |
|---|---|
/codelord:scan |
Codebase explorer — maps structure, stack, and conventions into your vault |
/codelord:search [query] |
Vault search — intent classification + grep + LLM reranking |
/codelord:drift |
Divergence detector — checks specs vs vault patterns vs actual code |
/codelord:graph [op] |
Knowledge graph analysis — health, orphans, clusters, hubs, synthesis opportunities |
/codelord:health |
Combined health report — graph + drift + link integrity |
| Skill | Description |
|---|---|
/codelord:connect [note] |
Forward connections — links a new note to existing vault notes |
/codelord:update [note] |
Backward pass — updates older notes to reference a newly created one |
/codelord:review [note] |
Quality audit — checks atomic note rules: one claim, valid links, good description |
/codelord:weave |
Missing link finder — detects plain-text references that should be wiki links |
| Skill | Description |
|---|---|
/codelord:seed [file] |
Queue a source file for full pipeline processing |
/codelord:document |
Immediate processing — extracts claims from a source without queuing |
/codelord:ralph N |
Phased queue processor — runs exactly N phases from the queue |
/codelord:pipeline [file] |
Full pipeline orchestration — seed → extract → connect → review in one command |
Obsidian — open your vault as an Obsidian vault to visualize the knowledge graph. Wiki links between notes become navigable edges. The graph view shows clusters, orphans, and synthesis opportunities that are hard to see in plain text.
Install superpowers alongside codelord.
claude plugin install https://github.com/obra/superpowersThe two plugins are complementary:
| codelord | superpowers |
|---|---|
| WHAT to build (specs) | HOW to build it (execution workflows) |
| WHAT was learned (vault) | HOW to build right (TDD, debugging, review) |
| Knowledge accumulation | Quality enforcement |
Key integration points:
| Before... | Use superpowers first |
|---|---|
| Writing a spec for a complex feature | superpowers:brainstorming |
| Any implementation | superpowers:test-driven-development |
Running /codelord:done |
superpowers:verification-before-completion |
The Lord operates on five principles:
- Vault = generalizable. Patterns that apply across projects live in the vault. Project-specific execution lives in
decrees/orspecs/. Never duplicate. Never confuse scope. - Specs = the contract. A spec is the agreement between intention and execution. Break it and you pay later — always later, always more.
- Context = sacred. Load only what the current task needs. Preloading speculatively burns context that doesn't come back. Every token counts.
- Drift = debt. The gap between what the spec says and what the code does is technical debt's invisible cousin. Surface it. Never accept it silently.
- Persistence = memory. What isn't captured is forgotten. What is forgotten, costs. Every session ends with
/codelord:done.
"The Lord never codes without a spec. He never lets knowledge die in a session. He never loads what he doesn't need."
- eidos — spec format that shaped how codelord thinks about behaviour-first documentation
- arscontexta — knowledge graph methodology that shaped how the vault is structured
MIT