helplisted

# X2 Help X2 in one paragraph: the kernel enforces the invariants in the build, so the skills only exist to capture human decisions at the right moments. The flow runs through three gates, each a prompted human turn that blocks the next phase: stories approved; the prototype approved at Claude Design and then approved again after copy-down (the lock); then ratified green, the audited exit report read and accepted. Green is declared by the slice-exit report and audited, never by prose. The sole metric is human turns per shipped slice, kept in a ledger file in the repo. ## The skills, in flow order | Skill | One line | Gate it requests | |-------|----------|------------------| | stories | Problem discovery to epic-level stories, one line each | Gate 1: stories approved | | seed | Create the repo from the edition, arm the CI gate, write CLAUDE.md constraints, start the ledger | none (setup) | | decompose | D-000 five-lens decomposition, persistent schema, slice one, deltas file | none (stays-ahead turns) | | design | Whole-product prototype and design system, in its own context | Gate 2a: prototype approved | | lock | Copy the prototype and full design system into the repo, verify, stamp provenance | Gate 2b: the lock | | derive-tests | Fidelity ledger and acceptance scenarios derived from the locked portion | none | | implement | Build all of the locked portion to green autonomously | none (the exit report checks the contract) | | slice-exit | The exit report: the definition