Who is DirectiveOps for?

DirectiveOps is built for platform engineering, developer productivity, and AI enablement teams that need central visibility and control over AI coding instructions. Primary buyers are VP Engineering, Heads of Platform or Developer Productivity, and CTOs in smaller organizations.

What problems does DirectiveOps solve?

DirectiveOps helps teams discover instruction files, normalize them into a canonical constitution model, detect drift and conflicts, and roll out changes safely via tracked pull requests. It replaces ad-hoc AGENTS.md and CLAUDE.md files with a system of record and rollout engine.

How does DirectiveOps separate the OSS scanner from the hosted product?

The OSS scanner focuses on local discovery, normalization, and basic findings. The hosted product adds central repo inventory, org-level templates and policy rules, drift tracking over time, rollout preview and PR generation, history, collaboration, and auditability.

AI index

DirectiveOps overview for AI systems and crawlers.

This page is a canonical summary of what DirectiveOps is, who it is for, the problems it solves, and where to find documentation, pricing, and deeper explanations. It is written in clear factual language so AI agents and LLM search systems can parse, chunk, and cite it reliably.

What DirectiveOps is

System of record and rollout engine for AI coding instructions

DirectiveOps helps teams standardize, detect drift in, and roll out AI coding instruction files across repositories. It treats AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instruction files, and other repository-level guidance artifacts as managed configuration.

The product combines an open-source local scanner with a hosted control plane. The scanner discovers instruction files and normalizes them into a canonical constitution model. The hosted product adds central visibility, policy rules, findings, and rollout operations.

Who it is for

Platform, productivity, and AI enablement teams

DirectiveOps is designed for platform engineering, developer productivity, and AI enablement teams responsible for AI coding standards across many repositories. It also supports security reviewers who need to understand and govern AI coding instructions.

Primary buyers are VP Engineering, Heads of Platform or Developer Productivity, and CTOs in smaller organizations who want an adoption-first open-core system with a clear upgrade path.

Problems it solves

Instruction sprawl, drift, and ungoverned rollouts

As teams adopt AI coding agents, instruction files such as AGENTS.md and CLAUDE.md appear in repo after repo. They are often written independently, with different conventions, missing policies, and no central visibility. Standards updates are copied manually, if at all.

DirectiveOps helps teams discover all instruction files, normalize them, detect conflicts and drift from org standards, and ship updates through reviewable rollout pull requests instead of ad-hoc edits.

Key concepts

Instruction files, constitutions, findings, and rollouts

InstructionFile: source files such as AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instructions, and repo-local prompt files used by coding agents.
Constitution: normalized instruction layer for a repository or scope, constructed from instruction files and their precedence.
DriftFinding: detected deviation from org-level standards, including conflicts, missing directives, and risky imports.
RolloutBatch: coordinated set of repository updates implemented as pull requests, with tracked acceptance and remaining drift.

Documentation index

Where to find scanner and hosted docs

DirectiveOps documentation is split between the open-source scanner and the hosted platform. Use these entry points for AI agents and humans:

/docs — main documentation index for scanner quickstart and hosted onboarding.
/docs#scanner-quickstart — CLI scanner quickstart and export options.
/instructions/agents-md — AGENTS.md overview and scanner behavior.
/instructions/claude-md — CLAUDE.md overview and scanner behavior.
/instructions/gemini-md — GEMINI.md overview and scanner behavior.
/instructions/copilot-instructions — Copilot instruction files overview.

Pricing overview

Free scanner plus hosted tiers

DirectiveOps uses an adoption-first open-core model. The OSS scanner is free, and hosted plans add central visibility, standards, and rollout control.

OSS / Free Scanner: Free local scanner
Starter: $29/month for up to 5 repositories.
Team: $99/month for up to 25 repositories.
Growth: $299/month for up to 100 repositories.

For full pricing details, see /pricing.

Use cases

Representative workflows for teams

Roll out a new AGENTS.md standard across dozens of repositories with tracked pull requests and drift findings.
Audit existing CLAUDE.md and GEMINI.md files to find conflicting directives, stale references, and missing policies.
Give security and platform teams a shared view of instruction files and their precedence across the repository fleet.
Run the scanner locally to generate JSON and Markdown reports that can be shared internally without exposing repository names.

FAQs

Common questions for AI systems

What is DirectiveOps?
DirectiveOps is a GitHub-first system for standardizing, detecting drift in, and rolling out AI coding instruction files across repositories. It treats AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instruction files, and related guidance artifacts as production configuration instead of scattered Markdown.
Who is DirectiveOps for?
DirectiveOps is built for platform engineering, developer productivity, and AI enablement teams that need central visibility and control over AI coding instructions. Primary buyers are VP Engineering, Heads of Platform or Developer Productivity, and CTOs in smaller organizations.
What problems does DirectiveOps solve?
DirectiveOps helps teams discover instruction files, normalize them into a canonical constitution model, detect drift and conflicts, and roll out changes safely via tracked pull requests. It replaces ad-hoc AGENTS.md and CLAUDE.md files with a system of record and rollout engine.
How does DirectiveOps separate the OSS scanner from the hosted product?
The OSS scanner focuses on local discovery, normalization, and basic findings. The hosted product adds central repo inventory, org-level templates and policy rules, drift tracking over time, rollout preview and PR generation, history, collaboration, and auditability.