teklabsdigital/x2-method

Performs a five-lens decomposition of project stories to define architecture, record persistent schema decisions, and plan the first slice. Use after repo seeding or when foundational decisions need revisiting.

Derive the fidelity ledger and acceptance scenarios from a locked prototype after gate 2b. Use only when a portion is newly locked or re-locked, never before.

Copy approved design prototypes into the repo, verify artifact completeness, and request explicit lock approval before derivation begins.

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.

Produces a comprehensive slice-exit report when a development slice is believed complete, serving as the definition of 'green' with evidence, audit trail, and methodology checks.

Use when starting an X2 project, when the problem domain has no approved epic story set, or when new scope needs stories added to an existing set. Runs problem discovery and produces epic-level stories, then requests gate 1 (stories approved).

Produces a whole-product prototype and design system from the source of truth when a design is needed, running in its own context separate from the builder. Also handles design gap revisions.

X2 Extract runs after an X2 project reaches a milestone to compute metrics, churn, and sanitized method-level findings from the turn ledger and decision records. It prepares candidates, confirmations, and negative-space nominations for a human rulings pass without exposing raw project material.

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 x2-method repo root.

Guides autonomous implementation of locked software slices, running tests to green with a strict human-turn contract and invariant enforcement.

X2 Kernel maintains the claims catalog, editions, and conformance records for the X2 method. Use it to add or retire claims, manage editions, measure enforcement, or verify the kernel stays coherent.

Diagnoses unknown runtime product misbehavior using structured observation, hypothesis testing, and minimal instrumentation to find root cause efficiently.

Migrates an existing project to the X2 development method by reconciling code, stories, and design, baselining documentation, and arming enforcement in CI. For use with legacy projects, not new ones.