ooj-tools

Plugins developed with agentic sensibilities in mind — tooling built for how coding agents actually work.

This repo is a Claude Code plugin marketplace and a Codex plugin marketplace. Each plugin lives under plugins/<name>/ with its own .claude-plugin/plugin.json (and, where it targets Codex, a .codex-plugin/plugin.json); the marketplace manifests at .claude-plugin/marketplace.json (Claude Code) and .agents/plugins/marketplace.json (Codex) list them.

Plugins

Plugin	What it does
dox	Deterministic AGENTS.md tree engine: injects the local AGENTS.md chain before edits (J1) and gates finishing on documentation drift (J3).
transcripts	Worktree-safe Claude Code and Codex transcript archives with configurable verbosity.
spec-to-tasks	Turn a PRD, spec, or MVP doc into a readable markdown task tree: parse into tasks, score complexity, and expand into subtasks — native skills, no MCP server or API keys.
plugin-configure	Cold-start profile setup: offers a curated skill/plugin profile on first launch in an unconfigured repo and writes it to .claude/settings.local.json.
ooj-skills	Every loose skill that doesn't warrant a plugin of its own, in one bundle: conventional-commits (a Conventional Commits message reference), asd-ste100 (ASD-STE100 Simplified Technical English), and readme (generate a standard GitHub-style README from the repo) — pure skills, no hooks or scripts.

Install

/plugin marketplace add /path/to/ooj-tools
/plugin install dox@ooj-tools
/plugin install transcripts@ooj-tools

(Or point at the GitHub repo: /plugin marketplace add oojBuffalo/ooj-tools.) Test a plugin in one session without installing — --plugin-dir loads a single plugin directory, not the marketplace root, so point it at plugins/<name> (repeat the flag per plugin to load more than one):

claude --plugin-dir /path/to/ooj-tools/plugins/dox

For Codex, add this repository as a marketplace and install the same source:

codex plugin marketplace add /path/to/ooj-tools
codex plugin add transcripts@ooj-tools

Adding a plugin

1. Create plugins/<name>/ with a .claude-plugin/plugin.json (and whatever components it needs — commands/, agents/, skills/, hooks/), following the plugin structure reference.
2. Add an entry to .claude-plugin/marketplace.json with "source": "./plugins/<name>" (schema: plugin marketplaces).
3. To also offer it in Codex, add an entry to .agents/plugins/marketplace.json (schema: build plugins). A .codex-plugin/plugin.json is optional — Codex falls back to reading .claude-plugin/plugin.json.

Adding a loose skill

A single skill doesn't get its own plugin. Drop skills/<skill>/SKILL.md into ooj-skills — the one bundle for every loose skill, whatever its topic — add a row to that bundle's README table, and bump its minor version. Reach for a plugin of its own only when the skill needs commands, agents, hooks, scripts, or an MCP server. The full convention lives in plugins/AGENTS.md.

If the plugin wants dox to maintain its own AGENTS.md tree, drop a .dox.json in its root (dox init) — the repo's git pre-commit gate (plugins/dox/hooks/git/pre-commit) checks every plugins/*/ that opts in.

Plugin-dev references

• Claude Code: plugins overview · plugin structure & manifest reference · marketplace schema · hooks reference
• Codex: plugins overview · build plugins & marketplaces · hooks · skills · openai/plugins (reference marketplace)

License

MIT for the collection; each plugin may carry its own license file (see plugins/dox/LICENSE) if it differs.