adoptlisted

# Adopting a project Every skill in this workflow reads `.claude/WSS.WORKFLOW.json`, and only this skill ever creates one; without it each skill degrades to conventional filenames and stays there. This skill is the way out, and the **only** one that runs before the project is under the contract at all. **It writes the `permissions.ask` entries of step 5 and nothing else with content in it.** The manifest itself goes through `manifest-writer`, which is its sole writer — this skill decides what the values should be and hands them over; the citation is [step 8's](references/WSS.STEP8-MANIFEST.md). The keys it may ask for are `WSS.MANIFEST.md`, cited from that same step; what the files those keys point at may be **called** is `WSS.NAMING.md`, cited from [step 9](references/WSS.STEP9-CREATE-RECORDS.md); who owns each record afterwards is [`WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md). **The first two are one pass and two reads.** An adoption settles a key and the name of the file it resolves to in the same breath, and they are separate contracts. ## What it is not **Not a rewrite.** If a manifest already exists this is an *amendment*: read it, report what it declares, fill only the gaps, and never overwrite a key the project already chose. **The one exception is a key or filename matching a previous suite convention** — the pre-rename `.claude/workflow.json`, a flat `workflow/v1` schema, an old record name. That is stale *machinery*, not a project's choice, and ame