Turn AI-assisted delivery into a governed local workflow — in any repo, any IDE.
54 skills · 9 agents · 6 surfaces · 1 governed flow
{ai} engineering installs a deterministic governance layer into any repository — specs, decisions, skills, agents, hooks, and an audit trail, all as versioned local files. No hosted control plane. No provider lock-in. Every IDE follows the same rules.
Quickstart
Get a governed repo in under a minute — {ai} engineering is uv-first:
uv tool install ai-engineering # install the CLI
ai-eng install . # add governance to your repo
ai-eng doctor # [PASS] hooks, mirrors, manifest, required tools
Prefer pip or pipx?
pipx install ai-engineering
# or
python -m pip install --user ai-engineering
Then open your editor and type /ai-start. Prefer to ease in? Start in observe mode and enforce only what proves useful.
What you get: 54 skills and 9 agents you invoke with /ai-<name> · a spec-driven workflow · automatic checks on every change · versioned local files you own. Update any time with ai-eng update.
The governed workflow
You drive the intent and approve each step; the gates catch the rest — no secrets, broken docs, or untested changes reach a merge.
The canonical chain is /ai-brainstorm → /ai-plan → /ai-build → /ai-pr. Use it whenever work changes product behavior, framework behavior, security posture, public docs, or release state. /ai-commit stays available for WIP checkpoints; it is not part of the chain.
Your toolkit
Fifty-four skills and nine agents cover the whole delivery loop — and the same commands work in every supported editor.
Need evidence? /ai-research returns cited findings from local context, the web, and async deep research. And because plans carry ready-to-apply patches, mechanical work routes to a smaller model — routine edits stay cheap.
Supported surfaces
One canonical payload is mirrored, byte-for-byte, into every enabled surface.
| Surface | Entry point |
|---|---|
| Claude Code | CLAUDE.md |
| GitHub Copilot | .github/copilot-instructions.md |
| OpenAI Codex | AGENTS.md |
| Antigravity | AGENTS.md + .agents/ |
| OpenCode | .opencode/ |
| Cursor | .cursor/ |
The ruleset lives in AGENTS.md. Project identity and hard prohibitions live in CONSTITUTION.md. Release history lives in CHANGELOG.md.
Highlights
- Ship a whole spec in one run —
/ai-autopilotdecomposes it, builds a dependency DAG, runs parallel waves, and converges on a reviewed PR. - What you approved is what shipped — a brainstorm hard-gate plus a spec-lifecycle state machine keep every change anchored to the approved spec (Rung 2 SDD — spec and code stay in sync, not just spec-first that drifts).
- An audit trail you own — every AI action lands in a hash-chained NDJSON log you can verify offline, with no telemetry by default.
- Every bypass has an owner and an expiry — no
# noqaor@ts-ignore; findings are refactored or formally risk-accepted with a severity-based TTL. - Every tool call is screened before it runs — a deterministic guard checks each edit, write, and shell command and stops risky ones.
- AI quality is a tested property — skills are measured with pass@k, and a regression beyond five points blocks the pull request.
Documentation
- ai-engineering.arcasiles.com — the website: what it is, why it's governed, and how to install
- docs/ — architecture, getting started, and the diagram set
- CONSTITUTION.md — mission, stakeholders, prohibitions
- CHANGELOG.md — release history and breakage notes
Standing on the shoulders of
{ai} engineering builds on ideas and patterns from these projects:
| Project | What we learned |
|---|---|
| Superpowers | Brainstorm hard-gate, TDD-for-skills patterns |
| review-code | Handler-as-workflow, parallel specialist agents |
| dotfiles/ai | Agent matrix, SDLC coverage |
| autoresearch | Radical simplicity as a design principle |
| SpecKit | Spec-driven workflow inspiration |
| Anthropic Skills | Frontend-design, skill-creator — absorbed and extended |
Contributing
Contributions are welcome. See CONTRIBUTING.md for development setup, code style, testing, and the pull request process. This project follows the Contributor Covenant Code of Conduct.
License
MIT. See LICENSE.
Star history
Contributors
Made with contrib.rocks.
1 maintainer
Metadata
1 maintainer
Release files for ai-engineering 0.13.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 | Provenance | |
|---|---|---|---|---|
| ai_engineering-0.13.0.tar.gz | 12.7 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_engineering-0.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.9 MB
Release files / ai_engineering-0.13.0.tar.gz
| Download URL | ai_engineering-0.13.0.tar.gz |
|---|---|
| Size | 12.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a7201bcd3b5dfc89f4ef45864d8f7688a326011ceb6485d658f69beefff9e43
|
|
BLAKE2b-256 checksum How to use checksums |
197ad9d2fc4dcc873961d2e3b65d554692e50b5dd9459dbc67a5cadbfdf213ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 27, 2026.
Transparency logRelease files / ai_engineering-0.13.0-py3-none-any.whl
| Download URL | ai_engineering-0.13.0-py3-none-any.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9bcee94a18f035d33d03d8d5fe9b50fca1c4335eeba1364da03c9bafb15bd88b
|
|
BLAKE2b-256 checksum How to use checksums |
bf73f8aaf1d313d4921ccfe05e9a9f1c2d06bae146e9cdf43257d6324fa141cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 27, 2026.
Transparency logSecurity for ai-engineering 0.13.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ai_engineering-0.13.0.tar.gz
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 Jul 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
