egrichlisted

# /egrich — full arm The seed alone is deliberately lean: `AGENTS.md` SSoT + bridges + `.agent/`, file-based coordination, no modules. `/egrich` is the opposite end — everything EG ships, wired and checked. **Say the cost out loud before you start.** The full stack adds always-on hooks, background processes (a live board server + bridges), and MCP servers. That is the right trade for a project running several agents in parallel; it is overkill for a solo repo. If the user has not clearly asked for "everything", name the cheap subset (§5) and let them choose — presented per Hyperbrief's setup-flow choice default (§5.6.9: plain floor band, costs/benefits + recommendation, "explain more simply" fallback). ## 1. Ensure the charter exists If `.agent/seed_prompt.md` is absent, run `/eg-bootstrap` (new project) or `/eg-migration` (existing rules) first, and continue only after it lands. If it is present but behind, run `/eg-upgrade` first — arming a stale charter just bakes the staleness in. ## 2. Install the plugin set ``` /plugin marketplace add SoliEstre/EstreGenesis /plugin install estregenesis@estregenesis-plugins /plugin install constellation@estregenesis-plugins /plugin install superscalar@estregenesis-plugins /plugin install hyperbrief@estregenesis-plugins /plugin install greatpractice@estregenesis-plugins /plugin install ultrasafe@estregenesis-plugins /plugin install compendium@estregenesis-plugins ``` ## 3. What each module gives the project — and what it costs Reg