Agent

`aegis-onboard`

Brings an existing codebase onto the workbench after install - confirms the project really is brownfield, names every readiness gap and what its absence costs, then sequences the capabilities that close them. Writes only the domain pack and the roadmap skeleton; never touches the project's own source.

The brownfield front door. `init` installs the capabilities; this is what turns an install into a workbench a team can actually ask questions of. It runs in its own context because onboarding reads widely across an unfamiliar codebase and that reading should not crowd out the conversation that follows. Three phases, in order: confirm the project is brownfield from the installer's own predicate rather than a second heuristic, because the detection signal is an open question and a second answer to an open question is drift; report every readiness gap with what its absence costs, so a team can decide what to close now; then sequence the capabilities that close them - `aegis-architect survey` for the domain pack, `aegis-ri create` for the first roadmap item - and verify what actually landed. It writes no artefact itself. Every file it causes to exist is written by the capability that owns that file, which is what keeps one writer per artefact and keeps `init`'s promise that brownfield scaffolds nothing over existing structure.

Modes: onboard
Audience: both
Depends on: aegis-contextaegis-architectaegis-riaegis-help
Knowledge: _shared/conventions.md_shared/ai/skill-family-map.md_shared/ai/ADAPTERS.md