Governed Agent SDLC is a cross-platform toolkit for AI coding agents. It separates a tool-neutral workflow kernel from project profiles and vendor adapters, so the same approval, security, artifact, review, and QA rules can be applied to different technology stacks.
The project is intentionally human-in-the-loop. It helps agents work predictably; it does not grant an AI permission to approve, merge, release, or retrieve credentials.
MVP status: the core workflow, Claude Code adapter, deterministic safety hooks, and cross-platform validation are available. Package publication and additional vendor adapters are intentionally future work.
What is included
- Six tool-neutral roles: architect, planner, developer, reviewer, QA, and publisher.
- A structured artifact lifecycle with explicit approval evidence and supersession.
- A TOML project manifest for repository layout, profiles, commands, and protected areas.
- A dependency-free Python CLI:
init,generate,validate,doctor, and artifact commands. - Claude Code agent generation and safety hooks.
- Stack profiles for generic repositories, Python, .NET, and Nuxt.
- Cross-platform tests and reusable GitHub Actions.
Quick start
Requires Python 3.11 or newer. From this repository:
python -m pip install -e .
agentkit doctor
agentkit validate
python -m unittest discover -s tests -v
Initialize another project:
agentkit init ../my-project --name my-project --adapter claude-code
cd ../my-project
agentkit doctor
Initialization is additive: existing AGENTS.md, manifest, core policy, hook, and adapter files are
not overwritten. A fresh project receives the generic stack profiles and a minimal AGENTS.md so
generated roles always have the instructions they reference.
Create and move a governed artifact:
agentkit artifact new spec add-search
agentkit artifact transition docs/agent/specs/<file>.md awaiting_approval
agentkit artifact transition docs/agent/specs/<file>.md approved \
--approved-by "github:maintainer" \
--evidence "https://github.com/org/repo/issues/123#issuecomment-..."
An agent must never supply approval metadata for itself. The human supplies the actor and durable evidence, and CI validates that the fields exist.
Project manifest
agentkit.toml or .agent/project.toml is the source of truth:
version = 1
protected_areas = ["authentication", "database-schema", "billing"]
[project]
name = "commerce"
topology = "monorepo"
[[repositories]]
id = "backend"
path = "services/api"
profiles = ["dotnet"]
[[repositories]]
id = "frontend"
path = "apps/web"
profiles = ["nuxt"]
[workflow]
require_spec = true
require_plan = true
require_review = true
require_qa = true
Repository paths are resolved from the manifest and must remain inside the project root. No machine or user-specific absolute path belongs in committed configuration.
Validation is strict and dependency-free. It rejects unsupported manifest versions and topology,
missing workflow flags, invalid field types, duplicate repository identities or paths, escaping
repository paths, and profile capabilities that are not provided by profiles/, adapters/, or
the repository's GitHub integration.
Artifact validation also checks kind-specific parent gates, approval history for approved/active/
completed/superseded states, repository and protected-area references, timestamps, supersession,
and metadata types. Artifact creation refuses filename collisions. Transitions made through the CLI
are restricted to Markdown files below the active project's docs/agent/ directory.
Design boundaries
core/is vendor-neutral and is the only source of workflow meaning.profiles/contain stack-specific commands and exclusions.adapters/and generated tool files translate the core; they do not redefine it.hooks/enforce deterministic safety rules. Prompts explain behavior but are not security controls.- Hook input is fail-closed: malformed input is denied, as are credential paths/environment dumps, force pushes, and direct protected-branch refspecs.
docs/agent/holds project artifacts, not hidden agent memory.
See Architecture, Workflow, and Adopting Governed Agent SDLC.
Maturity
Version 0.1.0 is an MVP. Claude Code is the first adapter. Codex and other adapters should consume the same core contracts rather than introduce parallel policy files.
License
MIT. See LICENSE.
Release files for governed-agent-sdlc 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| governed_agent_sdlc-0.1.0.tar.gz | 60.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| governed_agent_sdlc-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.9 kB
Release files / governed_agent_sdlc-0.1.0.tar.gz
| Download URL | governed_agent_sdlc-0.1.0.tar.gz |
|---|---|
| Size | 60.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92bf86ba6a59316fda0f187ebc8e3379696a095a32bb78bc4a21133c210d1bed
|
|
BLAKE2b-256 checksum How to use checksums |
debcd617b1da05ac433749c328ec8fa5f1d29bd6d511e1e09aa97829634f44f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / governed_agent_sdlc-0.1.0-py3-none-any.whl
| Download URL | governed_agent_sdlc-0.1.0-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dfaae27e282ac209773c87d49305036b0b160a795042f65387eb9b82b2514029
|
|
BLAKE2b-256 checksum How to use checksums |
0c0e530becda15a7f070e5a49f5d3db316180857f9ded218f432fa426c33e9a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency log