adopt-workflowlisted

# Adopting a project Every skill in this workflow reads `.claude/workflow.json`, and nothing else 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`](../../workflow/writers/manifest-writer.md), which is its sole writer — this skill decides what the values should be and hands them over. The keys it may ask for are [`manifest.md`](../../workflow/manifest.md); who owns each record afterwards is [`ownership.md`](../../workflow/ownership.md). ## 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. **Not a documentation pass.** It creates record files *empty*, with their heading and nothing else. Content is the owning skill's, always — an adopted project with an empty backlog is correct; one with a backlog this skill invented is a lie on day one. **Not a judgement about the project.** It reports what it found and what it could not resolve, and an unresolvable key is left **out** of the manifest: a missing key degrades gracefully and says so, while a key pointing at the wrong file misdirects every skill that reads it, silently. ## 1. Establish which mode y