adopt

# Adopt (brownfield entry) `/mycelium:start` assumes a blank page. Most projects are not a blank page. This skill is the entry point when the code came first. ## When to Use - A repo with existing source and no populated canvas (the SessionStart brownfield check points here). - A maintainer who wants discovery on a product that already ships. - NOT for a new idea — that is `/mycelium:start`. ## The shape of the run: two phases, one session **Phase 1 — populate from the codebase.** Read the repo and fill in what the code can actually establish, at the right evidence class. **Phase 2 — patch the holes with the user, exactly as a greenfield project would.** The gaps left by phase 1 are not a backlog to hand over. They are the agenda for the rest of the session, worked with the same discovery discipline `/mycelium:start` would apply — the only difference is that the canvas is not empty when you begin. Do not stop between the phases and present a list. Ending at a fork is the failure this skill exists to remove: a maintainer offered "run the greenfield brief or skip" has no good option, and "here is your discovery backlog" is the same fork with extra steps. **Why phase 1 cannot be the whole thing.** A codebase answers *what was built* and *how it ships*. It is nearly silent on *why it exists* and *who decided that*. Extraction is asymmetric, and inverted from where discovery value lives: | scale | what code yields | |---|---| | L4 Delivery | STRONG — stack, release cade...