菜单
Use when the builder believes the slice is green, to produce the slice-exit report that is the definition of green. Triggers before any green declaration and at slice close. Green is declared by the report and ratified only after intake audits it. Never declare a slice green in prose, and never skip a section because it is inconvenient.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when an existing project that was not built with X2 must be migrated to run under it, with documentation sprawl to dissolve, stories to harvest at epic altitude, an as-built design to baseline, and existing enforcement to map and arm. Runs the migration on a dedicated branch with three human gates. Do not use for a new project (that is seed), and do not use it to redesign the product or refactor code beyond what arming the enforcement requires.
Use after the repo is seeded to run the D-000 five-lens decomposition, record persistent schema decisions, define slice one, and start the deltas file. Also use when a stays-ahead decision (decomposition, schema) must be revisited. Do not use for per-slice implementation decisions; those are D-0xx record-gaps raised during implement.
Use when someone asks what an X2 skill does, which skill to run next, how the gates work, or where an artifact lives. A quick in-flight reference; for the method's rationale, read X2.md at the method repo root.
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.
Use to change the claims catalog (add, amend, retire a claim, cut a catalog pass), to manage editions (add, retire, recompose), to measure an edition's conformance honestly (plant, prove, audit, lower a row), to clear accumulated decisions with the owner, or to check that the whole kernel is still coherent. Also use when a claim or edition change may have left counts, scope or statements in the documentation stale. Do not use it to seed a project from an edition; that is seed's job.
Use when an X2 project completes (or reaches a major milestone) to run the extraction loop, the quality feedback that folds the project's evidence back into the method. Reads the turn ledger and decision records, computes the metric and the per-decision churn table, distils sanitized candidates, confirmations, and negative-space nominations, and holds everything for a rulings pass. Do not use mid-slice (that is the normal intake flow), and never let raw project material cross into the public method.
| name | slice-exit |
| description | Use when the builder believes the slice is green, to produce the slice-exit report that is the definition of green. Triggers before any green declaration and at slice close. Green is declared by the report and ratified only after intake audits it. Never declare a slice green in prose, and never skip a section because it is inconvenient. |
The definition of green. The pilot declared "all green" twice before it was true, and the true state had to be extracted by interrogation; every "confirm X" the human issued was the same turn shape, repeated because the method had no artifact in which the builder declares, with evidence, what green means. This report is that artifact, and it has teeth: a slice without a complete report is not green (MET-06).
Plus one standing check: any phase that started without its gate on record (stories, prototype approval, the lock) is a methodology violation and is surfaced here (MET-07).
Scripted where mechanical (tier counts, the coverage diff), authored where judgment is needed (deviations, pending rulings).
Intake audits the report before ratification. The builder does not grade its own green; "sound" is intake's word to give. The human's turn becomes reading one document, not extracting it.
Where the report lives: the pilot used the repo's working docs; the alternative is the extraction
record. Carried on the record; the pilot's docs/work/ is the working default until ruled.
