A Claude Code plugin that provides governance tools for human-AI collaboration based on the Outcomes-Driven Development (ODD) framework.
Outcomes-Driven Development is a governance framework that prioritizes real-world results over artifacts. The core thesis:
Development is about defining outcomes, enforcing constraints, and verifying reality—not writing code. AI accelerates execution; governance preserves trust.
- Prompt over Code - Intent guides generation; code is ephemeral
- KISS - Simplicity is non-negotiable
- DRY with Isolation - Reuse without brittle coupling
- Consistency - Behavioral predictability matters
- Maintainability - Systems must survive creator turnover
- Antifragile - Recovery paths preferred over prevention
- Scalable - Growth bounded in cost, complexity, and attention
- Claude Code version 1.0.33 or later
# Step 1: Add the marketplace
/plugin marketplace add unfoldingWord/odd-claude-plugin
# Step 2: Install the plugin
/plugin install odd-claude-plugin@unfoldingWordFor project-wide installation (shared with collaborators via .claude/settings.json):
/plugin install odd-claude-plugin@unfoldingWord --scope project# Clone the repo
git clone https://github.com/unfoldingWord/odd-claude-plugin.git
# Add as local marketplace
/plugin marketplace add ./odd-claude-plugin
# Install (use the plugin name from plugin.json)
/plugin install odd@odd-claude-pluginRun /plugin and check the "Installed" tab to confirm the plugin is active.
Initialize ODD governance in your project. Provides guidance on:
- The ODD framework and 7 pillars
- Core terminology (Outcome, Evidence, Artifact, Canon, Attempt, Lane)
- Document tiers (Tier 0-3 epistemic obligation levels)
- Project maturity levels (PoC → Pilot → Production)
- Recommended folder structure
Run through the 9-area self-audit checklist before declaring work complete:
- Intended Outcome
- Constraints Applied
- Decision Rules Followed
- Verification Performed
- Evidence Produced
- UX & Behavior Check
- Tradeoffs & Risks
- Maintainability Check
- Confidence Level
Check if work meets the ODD Definition of Done requirements:
- Change Description - What changed, where, and why
- Verification Performed - What was run or checked
- Observed Behavior - What actually happened
- Evidence Produced - Proof of behavior
- Self-Audit Completed - Reflection against constraints
Interactive PRD (Product Requirements Document) creation with:
- PRD Type Classification (PoC, Feature, Fix, Product slice, Refactor)
- Asset Intake (inventory existing docs, media, links)
- 7-Stage Elicitation:
- Outcome Discovery
- Success Criteria
- Non-Goals and Scope
- Constraints
- Definition of Done
- Risks and Tradeoffs
- Draft Assembly
Review and apply the 10 ODD constraints:
- Offline-First (Default)
- Long Timelines & Changing Ownership
- Maintainability Over Cleverness
- Interoperability Over Feature Completeness
- Stateless or Low-State by Default
- AI as Accelerator, Not Authority
- Evidence Over Assertion
- UX Is Contextual, Not Universal
- Ephemeral Artifacts Are Acceptable
- Explicit Tradeoffs
Get guidance from the 14 ODD decision heuristics when facing choices:
- Outcomes Before Implementation
- Borrow → Bend → Break → Build
- Simplicity Wins (KISS)
- DRY with Isolation
- And 10 more...
A dedicated PRD elicitation agent for thorough, multi-turn PRD creation. Key principle: "You extract. You do not invent."
Features:
- PRD type classification and asset intake
- Terminology precision enforcement
- Probing questions at each stage
- Push-back on vague or untestable statements
- Comprehensive PRD assembly
ODD applies different levels of rigor based on project maturity:
| Level | Stage | Governance |
|---|---|---|
| 0 | PoC / Exploration | Bias toward speed; over-governance prohibited |
| 1 | Pilot / Product | Evidence required; tradeoffs explicit |
| 2 | Production | Outcomes measurable; security mandatory |
Work is not complete unless it is verified with evidence. Assertions like "this should work" do not count.
Clean restarts with better constraints are progress. Restarting is not failure.
In AI-accelerated development, durable intent is scarce—not computation.
ODD uses precise vocabulary:
| Term | ODD Meaning | NOT |
|---|---|---|
| Outcome | Verifiable state that can be demonstrated | Feature, artifact, checkbox |
| Evidence | Observable proof (reproducible/recorded) | Confidence, assertion |
| Artifact | Byproduct of work. Ephemeral by default | The goal or proof of value |
| Canon | Curated truths earned through verification | Wiki or documentation dump |
| Attempt | Bounded execution with evidence captured | Vague "try" or experiment |
Full ODD documentation is available in docs/prd-guide-pack.md (v1.4.1), including:
- Core terminology and document tiers
- Complete constraints definitions
- All 14 decision rules with examples
- Definition of Done requirements
- Self-audit checklist details
- PRD template and creation guide
See docs/future-ideas.md for planned enhancements including:
- File creation in
/odd-init - Evidence capture helpers
- Maturity level tracking
- Code review integration
Contributions welcome! When contributing, please:
- Follow ODD principles (evidence over assertion)
- Include verification of changes
- Document tradeoffs explicitly
MIT
ODD is about preserving intent without freezing execution. The measure of success is not how elegant the artifact is, but whether the outcome holds up in the real world.