AEGIS is a set of agents, prompts and skills for GitHub Copilot in VS Code and for Claude
Code, backed by a Python tool layer. Orchestrator agents guide you one small step at a time. Specialist agents write
and maintain a set of living documents. The tooling validates those documents after every
change, so requirements, architecture and code stay consistent.
Why AEGIS
- One step at a time. Orchestrators ask a few focused questions, recap and wait for you.
You never get a 40-question form.
- Documents that stay consistent. Every artifact uses a fixed template and stable ids.
Validation runs after each edit, and a critic agent fixes what it finds.
- Grounded in your standards. Agents check your organization's Enterprise Standards
first, cite them, and ask only about what they leave open.
- Bounded, reviewed implementation. Code is written one approved work package at a time,
inside declared paths, and completes only with an independent review and recorded evidence.
- No automatic deployment. Release needs a named human approver.
Quick start
git clone https://github.com/nishant-tamilselvan/AEGIS.git && cd AEGIS
pip install -e .
Then open it in your agent host:
| GitHub Copilot | Claude Code |
|---|
| Open the folder in VS Code and switch Copilot Chat to Agent mode. | Run claude in the folder. See Using AEGIS with Claude Code. |
Other ways to get AEGIS:
- Claude Code plugin (preview): install AEGIS into your own repository instead of
working in a clone. Run
/plugin marketplace add nishant-tamilselvan/AEGIS, then
/plugin install aegis@aegis, then pip install aegis-sdlc. See
AEGIS as a Claude Code plugin.
- CLI only:
pip install aegis-sdlc gives you the artifact-tools command, for
example to validate artifacts in CI. See the CLI reference.
Start with the same command in Copilot or a Claude Code clone (the plugin uses
/aegis:start-ideation):
/start-ideation customer-portal A self-service portal where customers track orders
When ideation is done, continue with /start-architecture customer-portal, then
/start-implementation customer-portal <absolute-path-to-target-repo>.
The getting started guide walks through each phase.
⭐ Finding AEGIS useful? Star the repository
so other teams can discover it too.
How it works
flowchart LR
U[Raw idea] --> P1[1. Ideation<br/>6 business artifacts]
P1 --> P2[2. Architecture<br/>5 technical artifacts + ADRs]
P2 --> G{Readiness gate}
G -- blocked --> P2
G -- ready --> P3[3. Implementation<br/>bounded work packages]
P3 --> R[Independent review<br/>+ evidence]
R --> H[Human release approval]
| Phase | You get |
|---|
| Ideation | Product, functional and non-functional requirements, a user journey map, a system blueprint and an executive briefing. |
| Architecture | Interface specifications with native contracts, data, security, deployment and observability architecture, and ADRs. |
| Implementation | Work packages traced to the artifacts, a decision ledger, and reviewed code in your target repository. |
Artifacts live in docs/artifacts/<app-name>/, one folder per application. See
how it works for the artifacts, ids and guarantees, or browse a
complete example for a simple to-do app: every phase 1 and
phase 2 artifact, an OpenAPI contract and two ADRs, all approved and ready for
implementation.
What's inside
| |
|---|
| 18 agents | 3 orchestrators and 15 specialists across the three phases. Catalog. |
| 10 prompts | Slash commands to start, resume, review and change each phase. List. |
| 2 hosts, 3 setups, 1 source | Everything is written once in aegis/ and generated for GitHub Copilot (.github/), Claude Code (.claude/) and the Claude Code plugin (plugins/aegis/). |
| 4 skills | Artifact, ADR and implementation management, and Enterprise Standards grounding. |
| Hooks | A guard before implementation tool calls, and validation after every edit, in every setup. The plugin adds a session-start hook that loads the golden rules. |
artifact_tools CLI | Scaffold, validate, ADRs, contracts, diagrams and implementation state. On PyPI as aegis-sdlc. Reference. |
| Reference MCP server | Serves your standards from Markdown files. Setup. |
Where AEGIS fits
AEGIS is a reference implementation of the
Enterprise AI Framework
delivery model. The framework describes the process: a specification before code,
lifecycle gates
and a named human who approves the release. AEGIS runs that process in your editor.
| Resource | What it gives you |
|---|
| Delivery model | The process AEGIS follows, independent of any tool |
| Reference implementation page | How each part of the framework maps to AEGIS, and what AEGIS does not cover |
| Starter standards library | Six framework rules in the format the reference server reads. They start as Draft, so your organization reviews and approves them first. |
The same person maintains both projects.
Enterprise Standards
Connect your organization's standards, policies, patterns and enterprise decisions through
a read-only MCP server named enterprise-standards-server. You can run the included
reference server on a folder of Markdown files, put
your own server in front of an existing system, or run without one. The
setup guide covers each option.
Security
The implementation guard is a safeguard, not a sandbox. Review what agents change before
you merge it, and treat standards content as untrusted input. Report vulnerabilities
privately. See SECURITY.md.
Contributing
Contributions are welcome. See CONTRIBUTING.md for the setup, the
checks CI runs and a checklist for each kind of component. This project follows the
Code of Conduct. Changes are recorded in the changelog.
Support the project
If AEGIS saves you time, please:
License
MIT
