← ClaudeAtlas

seedlisted

Use immediately after gate 1 (stories approved) to settle which kernel edition the project is built on, create the project repo from it, and make the method durable inside it. Also use when an existing X2 project is missing its CLAUDE.md standing constraints or its turn ledger. Do not use before stories are approved, and never use it to modify the kernel itself.
teklabsdigital/x2-method · ★ 15 · AI & Automation · score 65
Install: claude install-skill teklabsdigital/x2-method
# X2 Seed Copy the kernel down, initialise it to the product, and anchor the method in the repo. Seeding runs right after gate 1 so the repo exists before any decision work: D-000, the behaviour spec, and the prototype import all need a home, and the standing constraints and ledger must be repo-anchored from the first turn. The pilot instantiated late and the missing scaffolding cost roughly a quarter of all measured turns (INV-03); its pasted-prompt constraints decayed under compaction into 55 violations (MET-08). Seed exists so neither happens again. ## Steps 1. **Create the repo.** A new sibling repo named for the product, decided at ideation. 2. **Settle which edition.** The kernel ships more than one, and they are not interchangeable: an edition is a stack, a store and a test tier set, and the choice binds every slice after it. It is the owner's, so ASK rather than infer, and ask before the manifest is opened, because the manifest that answers "what does a seeded project receive" is the chosen edition's and no other. Do not read a preference out of the product idea, and do not default to whichever edition the kernel lists first. Record the answer where the record already has a home for it: the kernel-provenance row carries the edition beside the pin, so a project can always say which mechanism set its conformance statement refers to. If the request already names a stack, that IS the answer and no turn is owed. 3. **Instantiate that edition per its