agentleFS
nishant-tamilselvannishant-tamilselvan/AEGIS/docs/agents.md

AEGIS

AGENTS.md1 starsChanged 48 days agoMITView on GitHub

Agents are written once in aegis/agents/ and generated for GitHub Copilot (.github/agents/), Claude Code (.claude/agents/) and the Claude Code plugin (plugins/aegis/agents/). Orchestrators talk to you. Specialists do focused work and report back to their orchestrator. In Claude Code, orchestrators run in the main conversation and specialists run as subagents; see Using AEGIS with Claude Code. In the Claude Code plugin, every name below carries an aegis: prefix: agents such as aegis:artifact-manager, and commands such as /aegis:start-ideation. Prompts are written in…

The file

Files
agents.md

Agents, prompts and skills

Agents

Agents are written once in aegis/agents/ and generated for GitHub Copilot (.github/agents/), Claude Code (.claude/agents/) and the Claude Code plugin (plugins/aegis/agents/). Orchestrators talk to you. Specialists do focused work and report back to their orchestrator. In Claude Code, orchestrators run in the main conversation and specialists run as subagents; see Using AEGIS with Claude Code. In the Claude Code plugin, every name below carries an aegis: prefix: agents such as aegis:artifact-manager, and commands such as /aegis:start-ideation.

Ideation (phase 1)

AgentRole
ideation-orchestratorUser-facing. Runs the phased conversation without overwhelming you.
architectureProposes the smallest system blueprint that meets the requirements.

Architecture (phase 2)

AgentRole
architecture-orchestratorUser-facing. Guides interfaces, data, security, deployment and observability in turn.
interface-integration-architectProposes API and event contracts, and the observability strategy.
data-architectProposes the data model, retention and data sovereignty.
security-architectProposes the threat model, identity and access, and trust boundaries.
platform-architectProposes the deployment topology, environments and disaster recovery.
adr-authorRecords architectural decisions as ADRs.

Shared by phases 1 and 2

AgentRole
artifact-managerThe only writer of artifacts. Assigns ids, bumps versions and validates.
critic-reviewerRead-only quality gate. Drives self-correction until validation passes.

Implementation (phase 3)

AgentRole
implementation-orchestratorUser-facing. Runs readiness, human checkpoints, execution and release.
implementation-plannerRead-only. Turns approved artifacts into bounded work packages.
data-contract-implementerMigrations, persistence, contracts and shared types.
service-implementerAPI, domain and integration code.
ui-implementerAccessible UI built on the target's design system.
platform-implementerCI/CD, containers, manifests and operational wiring. Never deploys automatically.
test-quality-engineerIntegration, end-to-end, performance and security verification.
implementation-reviewerIndependent, read-only package and release review.

Prompts

Prompts are written in aegis/prompts/ and run as slash commands in Copilot Chat and Claude Code. Most take the application name as their first argument.

PromptRunsUse it to
/start-ideationIdeation OrchestratorStart a product from a one-line idea.
/add-requirementIdeation OrchestratorAdd or change a requirement and propagate it.
/start-architectureArchitecture OrchestratorStart phase 2 from the business artifacts.
/add-adrADR AuthorRecord a significant architectural decision.
/run-review-cycleCritic ReviewerRun a full self-correction review over the artifacts.
/start-implementationImplementation OrchestratorStart phase 3 against a target repository.
/resume-implementationImplementation OrchestratorResume phase 3 after checking for drift.
/implementation-statusImplementation OrchestratorReport progress, coverage and blockers (read-only).
/add-implementation-decisionImplementation OrchestratorRecord a tactical choice or escalate a material one.
/run-implementation-reviewImplementation ReviewerReview a work package or the final release.

Skills

Skills are written in aegis/skills/ and copied to all three setups. Agents load them when a task needs them.

SkillCovers
artifact-managementAuthoring and validating the artifacts, with templates and id conventions.
adr-managementCreating, indexing and superseding ADRs.
implementation-managementPhase 3: readiness, work packages, decisions, evidence and the release gate.
enterprise-standardsQuerying the Enterprise Standards library before each phase.
writing-stylePlain, readable prose, with a rule file and a checker script.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.