oah helps you build an AI development workflow that fits you and keeps changing as AI improves. It is a working reference and a guide you can adapt.
A useful result needs more than generated code: the scope must be clear, the changes checked, and decisions kept for the next session. oah connects those steps so one request can carry through the work with a record of what happened.
002 / Why it keeps changing
Older rules and skills can hold a newer model back or make its results worse. Defaults should be easy to understand and change; a rule that gets in your way is a design problem to fix.
Keep the parts that help, remove what no longer helps, and revise the workflow as your tools improve. You can start with the full setup or take only the impact map, wiki, leases, evidence gates or review loop that your project needs.
003 / Why Claude builds and Codex reviews
This split comes from the author's own experience, not a measured comparison: Claude fills in details a beginner might miss in a first version; Codex checks and corrects within a fixed scope.
The current commands run Claude Code and Codex CLI. The ideas can also be adapted to another tool or harness, with one AI or several. Give each stage to the AI that suits your work.
004 / From one request to a checked change
Describe the result you want in plain language. The AI records the goal and scope, checks what the change touches, reserves its paths and chooses the tools for the task. Claude builds; Codex reviews, corrects and reviews again.
Gates record the checks and their results. The project wiki keeps the decisions and reasons beside the code. In v0.3.0, optional TypeSafe Jev can judge difficulty for model selection; rules remain the fallback when it is unavailable or uncertain.
005 / The decisions stay with you
You ask, answer when the AI needs a decision, and confirm before the change lands. If the same problem repeats or the work reaches a design choice, the loop stops to ask you.
Ask “Is the review done?” or “Did all the gates pass?” and inspect the evidence. The final confirmation belongs to you; writing code, checking it and approving its landing are separate steps.
006 / Free, open source, yours to adapt
oah is free, open-source software under the MIT license. Read the source, change it and bring the useful pieces into your own workflow. Your AI services and any optional services use their own accounts and billing.
The current v0.3.0 release supports macOS and native Windows, and expects familiarity with git and pull requests. Install it, run oah init in your project, then try the small hello-oah example. The installation and documentation sections explain each step.
The toolkit is the set of skills, plugins, MCP servers and command-line tools oah recommends, each with its source and license. Skills whose license allows it are bundled byte for byte at a pinned commit; others are linked with their official install command. MCP templates hold placeholders, never key values, and pin an npm version.
When you need it
Skills and plugins copied from around the web lose their license and origin, may carry secrets, and change underneath you without notice.
How it works
Bundled skills live under skills/<name>/ with the upstream license and an UPSTREAM.json record: computer-use, orca-cli, orchestration, typesafe-ai, skill-creator, mattpocock-skills, codex-plugin-cc, ponytail, and the opt-in, regional humanize-korean.
Linked items — unlazy, superpowers, graphify, vercel-react-best-practices, the Anthropic document skills and lazycodex — ship only their install command and source, because of their license or this repository's privacy scan.
MCP templates in mcp/ (context7 and mcp-openai) use ${NAME} placeholders (Claude) or env_vars names (Codex) and pin an npm version; Aside and openaiDeveloperDocs are linked.
oah skills list shows bundled, cached, linked and installed skills with version, source, license and location; oah skills install <name> copies a bundled skill under its own short lease after showing the plan.
oah doctor checks the recommended command-line tools and prints their official install commands.
Example
Copy a bundled skill into this project (from Toolkit).
oah skills install computer-use
Requirements
Optional CONTEXT7_API_KEY and OPENAI_API_KEY for the MCP templates, read by Claude Code or Codex when they start the server.
Limits and recovery
Owner-specific or private skills, account-bound connectors and tools that ship inside another product are excluded; only their counts are listed.
Two OS accounts sharing one skill folder are not coordinated; run their commands separately.
A proxy URL with embedded user information is refused.
oah never edits mcp/, the catalog or your MCP config; it only notifies about newer versions.