---
name: Seed
slug: seed
category: DevOps
description: Creates the project repo from the kernel edition, anchors standing constraints and turn ledger, and verifies CI and branch protection are armed. Use right after gate-1 stories approval or to repair a missing CLAUDE.md/ledger in an existing X2 project.
github: "https://github.com/teklabsdigital/x2-method/tree/master/skills/seed"
language: "C#"
stars: 12
forks: 1
install: "git clone https://github.com/teklabsdigital/x2-method"
added: 2026-07-16T13:43:29.644Z
last_synced: 2026-07-16T13:43:29.644Z
canonical_url: "https://dirskills.com/skills/seed"
---

# Seed

Creates the project repo from the kernel edition, anchors standing constraints and turn ledger, and verifies CI and branch protection are armed. Use right after gate-1 stories approval or to repair a missing CLAUDE.md/ledger in an existing X2 project.

**Install:** `git clone https://github.com/teklabsdigital/x2-method`

## README

# 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. **Instantiate the edition per its manifest.** The edition README's "Instantiation manifest"
   section is the definition: the file set (A), the ordered setup steps (B), and the verify-as-a-set
   list (C). Run all three parts and verify part C as a set, not one by one from memory. The
   manifest's contents are the kernel's to define; this skill runs it and does not restate it. Two
   points the record proved sharp:
   - Renaming Kernel to the product includes config values, not only code identifiers (the pilot
     shipped an issuer still named "kernel").
   - The CI workflow moving to the repo root is not the gate. Branch protection requiring it is,
     and it must be verified armed, not assumed (TEST-3's one honest asterisk). The same arming
     step covers HUM-1: code-owner review required, with `@OWNER` in CODEOWNERS renamed to the
     product owner; the manifest's verify list includes proving it with a test PR.
3. **Write the repo CLAUDE.md.** Standing constraints live here because repo files re-enter every
   session and survive any compaction; a pasted handover may restate them but the repo copy is
   authoritative (MET-08). Method constraints, always present:
   - Never commit unless explicitly directed.
   - Least code that solves the problem. YAGNI. Standard library over wrappers.
   - Pin exact versions, no floating, per the standing version policy. The cooling-off window is
     ruled (invariants pass, 2026-07-11): 90 days, and the number lives in ONE place, the project's
     `VERSIONS.md` header, copied down from the edition; cite it from there, never restate it.
     Container images pin tag@digest and get a ledger row like any package.
   - The turn-report shape and the rule that intake's classification governs (both decayed under
     compaction in the pilot; see the ledger section).

   House style, owner's preference: keep, replace or drop these, and record whichever set the
   owner chooses. What the method requires is only that the chosen set lives here and that any
   mechanically checkable rule ships its check:
   - Never use em dashes or en dashes, anywhere, including code and docs. Self-check with literal
     bytes, because BSD grep silently misses a BRE class:
     `grep -rn "$(printf '\342\200\224')" .` (em) and `grep -rn "$(printf '\342\200\223')" .` (en).
   - No professional disclaimers. Push back with reasons.
4. **Create the turn ledger.** An append-only file in the repo (the pilot used `docs/work/`). The
   builder appends every human turn the moment it happens: number, what happened, why a human was
   needed, provisional bucket. Every turn is fed to intake as it happens, not only defects; intake
   classifies, and its bucketing governs (MET-05). Backfill the gate-1 ideation turns from
   stories now, so nothing lives only in a compactible context.
5. **Land the behaviour spec.** If stories produced one, write it into `design/` beside where
   D-000 will live, so the design step has its behaviour source before it runs (MET-02's gap).

## Human-turn contract

- No gate of its own. Seeding is sanctioned stays-ahead setup; per the measurement rule it is not
  counted in turns per shipped slice. Any real decision it forces (an environment choice, a
  manifest gap) is logged as a turn like any other.
- A manifest gap discovered while seeding is a finding for the invariants pass, reported to intake,
  never patched into the kernel from here.

## What this skill must NOT produce

- No product decisions, no code, no schema, no design artifacts.
- No edits to the kernel edition or claims; report defects, do not fix them.

## Next

decompose.