Agentic Development#
The Agentic Development framework makes an organization the operating boundary for human and agent work. Each organization identifies a canonical documentation repository; every product repository carries a short router that points to that source and keeps its own nuance in the files a human already reads.
A repository adopts the framework by carrying a short router and the client routes that reach it, and by letting agents read outward — the repository's own files first, then the organization documentation, then the current task. The organization selects which context applies; the reading order decides what is read first.
| Page | Description |
|---|---|
| Spec | Requirements for fresh, index-first agentic development through canonical documentation and thin pointers. |
| Design | How the agentic development framework is built — OKF documentation, thin repo pointers, and deterministic context resolution. |
| AGENTS.md Template | The repository-level agent router template and the guidance for applying it. |
| MCP Servers | How one logical set of tool servers is defined once and declared by every runtime in its own format, so a documented procedure does not depend on which client runs it. |
| Runtime Integration | How a runtime is wired into the framework — the entry file it reads, the lifecycle point where it verifies context freshness, the permissions it needs, and what a new runtime must supply to be supported. |
| Plugin Distribution | How recurring workflows are packaged as named intents that point to canonical documentation, and why a packaged shortcut never carries a copy of the procedure. |
| Plugin Marketplaces | How shared and initiative-owned Agent Plugin marketplaces are named, laid out, versioned, and updated. |
| Agent Interaction | How humans and agents coordinate through issues, labels, and pull requests, and why intent and implementation are kept in separate artifacts. |
| Advisory Agents | The pattern for automation that analyses work and publishes its conclusion as advice, without deciding, relabelling, or committing. |
| Conformance | What a repository must provide to be conformant with the agentic development framework, what it may add, and the duplication checks that keep the router thin. |
| Agentic Development decisions | Immutable records of one-way-door choices in the agentic development framework. |