Outline-Driven Development

Formerly the ODIN Claude Plugin. The repository URL is unchanged.

Outline-Driven Development, nicknamed ODIN, is a highly opinionated code-agent skill library: principles-first engineering, surgical editing, and workflow automation, published as installable plugins. It gives you a drop-in skill set with five discipline layers. Skills are authored once in-tree, and every supported client discovers them from that same layout, so nothing is copied or republished.

Methodology: outline-driven-development · Site: outlinedriven.github.io

• 657 skills in 28 plugins, each authored once at plugins/<plugin>/skills/<slug>/SKILL.md
• Five harness surfaces from one tree: Claude Code, Codex, Cursor, Grok, and Kimi
• No package manager for the tooling; every script is dependency-free Node ESM or standard-library Python
• Six output styles in odin-core, each embedding the canonical doctrine byte-identically
• Pre-commit gates that audit the whole tree on every commit, listed in .pre-commit-config.yaml

Contents

• What is this
• Install
• Choose your plugins
• Using the skills
• Plugins
• Core philosophy
• Output styles
• Development
• License

What is this

657 skills in 28 plugins. A skill is authored once, at plugins/<plugin>/skills/<slug>/SKILL.md, and that path is its only home. The directory states which plugin owns the skill, so no registry has to answer that question. Every plugin and marketplace ships at one releaseVersion, currently 2.1.5, held in catalog/plugins.json.

Each harness resolves components from fixed conventions at the plugin root, so this layout is the one every supported client already discovers. Nothing is copied at publish time, and nothing is published to a package registry.

plugins/odin-core/
  .claude-plugin/plugin.json   Claude Code manifest
  .codex-plugin/plugin.json    Codex manifest
  .cursor-plugin/plugin.json   Cursor manifest
  .grok-plugin/plugin.json     Grok manifest
  .kimi-plugin/plugin.json     Kimi manifest
  skills/necessary-work/SKILL.md        authored skill
  skills/necessary-work/agents/openai.yaml   generated from the frontmatter
  mcp.json                     MCP servers, odin-core only
  output-styles/               Claude output styles, odin-core only

odin-core carries the six output styles and the planning skills; odin-code carries the day-to-day engineering skills. Install the rest by working domain.

Core philosophy

1. Investigate before acting. Never speculate about code you have not read.
2. Draw the structure before building it.
3. Match rigor to risk.
4. One logical change per commit.
5. Show the code, not a description of the code.

Install

Six install surfaces are supported; each installs from this repository.

Claude Code

claude plugin marketplace add OutlineDriven/odin-claude-plugin
claude plugin install odin-core@odin-marketplace

# Your selected plugin modules; Keep it lean, only for you.
claude plugin install odin-code@odin-marketplace
claude plugin install odin-run@odin-marketplace
claude plugin install odin-planning@odin-marketplace
claude plugin install odin-knowledge@odin-marketplace

# More ...

Codex

codex plugin marketplace add OutlineDriven/odin-claude-plugin
codex plugin add odin-core@odin-marketplace

# Your selected plugin modules; Keep it lean, only for you.
codex plugin add odin-code@odin-marketplace
codex plugin add odin-run@odin-marketplace
codex plugin add odin-planning@odin-marketplace
codex plugin add odin-knowledge@odin-marketplace

# More ...

Cursor

Add the marketplace, then /plugin install odin-core. Cursor reads the .cursor-plugin/plugin.json manifest at each plugin root.

/plugin install odin-core

# Your selected plugin modules; Keep it lean, only for you.
/plugin install odin-code
/plugin install odin-run
/plugin install odin-planning
/plugin install odin-knowledge

# More ...

Individual (gh skill)

gh skill installs a single skill for any of its supported agents. Passing the exact path skips a full tree traversal, which matters at this repository's size.

gh skill install OutlineDriven/odin-claude-plugin plugins/odin-planning/skills/askme \
  --agent <agent> --scope user

<agent> is claude-code, codex, cursor, grok, or kimi-cli.

Grok

grok plugin marketplace add OutlineDriven/odin-claude-plugin
grok plugin install OutlineDriven/odin-claude-plugin#plugins/odin-core

The #plugins/<plugin> suffix selects one plugin subdirectory from the repository.

Kimi

From a local clone; Kimi cannot install a subdirectory of a GitHub repository.

/plugins marketplace /path/to/odin-claude-plugin/.kimi-plugin/marketplace.json
/plugins install /path/to/odin-claude-plugin/plugins/odin-core

Both paths are absolute: Kimi rejects a relative plugin root.

Choose your plugins

Nothing here is all-or-nothing. odin-core and odin-code are the base from Install; every row below is what you add on top for that kind of work, and the rest of the 28 stay uninstalled.

Working on	Add
Everyday code changes	odin-run, odin-git
Tests and verification	odin-testing
Large refactors, audits, bounded iteration	odin-code, odin-review
A specific language	odin-python, odin-typescript, odin-native, odin-apple, or odin-formal
Web and interface work	odin-web, odin-design
Security review and hardening	odin-security, odin-fuzzing
Research and technical writing	odin-research, odin-knowledge, odin-writing
Product, planning, and new artifacts	odin-planning, odin-product, odin-visual
Building agents	odin-agent, odin-skills
Infrastructure and data	odin-infra

Each name installs with the same command:

/plugin install odin-security@odin-marketplace

The largest plugins are odin-native at 138, odin-run at 46, and odin-knowledge at 41. Install one skill instead of a whole plugin with gh skill install, shown under Install above.

Using the skills

You install plugins once and invoke skills every day. Start with the getting-started guide to run your first skill. Read using the skills for the invocation mechanics. Browse example workflows for chains mined from real sessions.

Plugins

Plugin	Category	Plugin	Category
odin-core	Coding	odin-knowledge	Productivity
odin-planning	Productivity	odin-learn	Productivity
odin-critique	Productivity	odin-people	Productivity
odin-product	Productivity	odin-agent	Productivity
odin-code	Coding	odin-skills	Productivity
odin-review	Coding	odin-writing	Writing
odin-testing	Coding	odin-visual	Design
odin-git	Coding	odin-design	Design
odin-release	Coding	odin-web	Coding
odin-run	Coding	odin-typescript	Coding
odin-infra	Infrastructure	odin-python	Coding
odin-security	Security	odin-native	Coding
odin-fuzzing	Security	odin-apple	Coding
odin-research	Research	odin-formal	Coding

catalog/plugins.json is the identity ledger: it holds each plugin's name, description, category, and tags, and every manifest and registry is generated from it.

Output styles

Output styles shape how the agent communicates. Switch through Claude Code's /config or by setting outputStyle in settings.json. They ship in odin-core.

• ODIN: default. Skeptic register, scope discipline, no reflexive validation.
• AxiomMode: formal-logic English with predicate-form claims and ASCII keywords.
• Builder: for non-technical builders. Outcome-first, plain language, progressive disclosure.
• Duet: companion to the duet skill. Decisions before prose, forks stated loudly.
• Linus: Torvalds review discipline. Good taste as special-case elimination.
• Eval: benchmark harness register, generated by margin-runner. Do not hand-edit.

Every style embeds a byte-identical copy of system-prompt-baseline.md, because the Claude Code loader does not resolve references. scripts/sync-baseline.py owns that copy.

Development

There is no package manager here. Every script is dependency-free Node ESM or standard-library Python.

just              # list tasks
just render       # regenerate skill manifests, plugin manifests, registries, skill index, and the doctrine cascade
just check        # every gate
just verify       # every gate plus Agent Skills validation

.pre-commit-config.yaml is the gate list. Every gate audits the whole tree and runs unconditionally, so none of them can be skipped by touching the wrong file. docs/specs/gates.md explains what each generator writes, what each gate proves, and how to read a failure.

License

See LICENSE. Third-party attribution is in licenses/NOTICE.

Issues: https://github.com/OutlineDriven/odin-claude-plugin/issues