Dokugent Plugins¶

⚠️ Preview Notice Plugin support in Dokugent is under active development. This documentation is intended for early adopters, contributors, and internal tooling. Official support, CLI commands, and plugin registry functionality will be announced in the public beta release.

Dokugent CLI was built to be extensible — because no single agent system fits all use cases. Plugins let developers shape their own agent ecosystems, enforce custom policies, and extend trust into the tools that matter to them.

Why Plugins?¶

Core commands like plan, criteria, and certify define the structure — but plugins define the reach.

Use plugins to:

Enforce organization-specific agent standards
Introduce new scaffolding templates for your workflows
Integrate with external systems (like Git, CI/CD, or cloud agents)
Automate inspections, simulations, or re-certifications

Plugin Types¶

Type	Description
`template`	Adds custom `init` blueprints
`linter`	Applies custom review or criteria checks
`runtime`	Hooks into agent output for logging or trace injection
`integrator`	Connects Dokugent to external APIs

➡️ For the complete JSON structure, field definitions, and schema rules, see the Plugin Spec.

Examples¶

dokugent-plugin-llama Adds support for configuring LLaMA-based agents via plan.md
dokugent-plugin-gitwatch Automatically triggers certify when tracked agent files change

Philosophy¶

Plugins should extend trust, not just behavior. Every plugin should aim to make agents more transparent, more accountable, or more aligned with human intent.

Contribute¶

Want to build your own? Start with:

dokugent init --plugin my-plugin-name

Coming soon: - Plugin registry to discover trusted extensions - Plugin certification system to verify safety, traceability, and compliance

Let’s build an ecosystem where trust isn’t optional — it’s the default.