Menu
Land the session — claim, born-red card first, READY PR, batched work, close-out docs, flip complete last; land on green.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cut + publish a substrate-kit release — version bump PR, workflow_dispatch publish, three-way asset verification, adopter distribution wave.
Roll a kit release out to one adopter repo — download, sha256 three-way, banked rollback, carve-out scan, born-red PR, tree-verified merge.
Resolve every reference in the ask before acting — inventory, resolve or search each one, report unfindables explicitly, state the assembled picture back (Q-0273 seed skill).
Hand the owner finished steps, not directions — deep links, paste-ready blobs, his path walked once, one batched sitting, payoff + verification stated (Q-0273 seed skill).
The checkpoint at natural pauses — should this action also be executed? does this lesson deserve a permanent home shippable NOW? Route via the table (Q-0273).
Turn a fragmented owner ask into main ideas, a restated fuller picture, a skill-index map, and structured-choice owner questions — before building (understand-and-reflect, executable).
| name | session-close |
| description | Land the session — claim, born-red card first, READY PR, batched work, close-out docs, flip complete last; land on green. |
Land venture-lab's session correctly — the full landing path, claim to merged-on-green. Playbook-grade: a session reading this executes without improvising (grounded-skills plan §7.2).
Drives the session's work to a terminal, verified state on two rails: the born-red gate (card first, flip last) and landing your own green PR (merge it directly once required checks pass, or let the server-side auto-merge-enabler land it — either is fine). Everything else is ordered steps.
control/claims/<branch-or-scope>.md, a single bullet: backticked
branch/scope token · scope — one-line detail · expected files/area ·
ISO date (the shape check_claims parses). Land the claim on main fast,
then re-read control/claims/ at HEAD before building..sessions/<date>-<slug>.md whose
Status badge line declares in-progress (the born-red hold token), plus
a one-line "what is about to happen". Push, then open the PR READY (not
draft) immediately: the open PR + the claim are the in-flight signal
parallel sessions collide without.do-not-automerge-
labelled PR waits for the owner. Read a red on a born-red head as the
designed hold, not a CI failure: verify any red against the job log
before diagnosing — alias/mirror jobs echo the required check without
running anything (kit repo example: the two legacy jobs mirroring
kit-quality), and "HOLD (by design)" means nothing to investigate.docs/CAPABILITIES.md (dated, with its venue token, exact error or
proof, workaround — below the seed fence, never inside it); every
⚑ needs-owner ask carries the OWNER-ACTION fields (WHAT / WHERE / HOW /
WHY-IT-MATTERS / UNBLOCKS / VERIFIED-NEEDED — attempted, or the exact
wall; see control/README.md) — Withdraw stale asks; groom one idea
forward; add one new 💡 idea you genuinely believe in; write the ⟲
previous-session review.python3 bootstrap.py check --strict and python3 bootstrap.py check --strict.
The only acceptable pre-flip red is the designed born-red hold naming
this session's own card.complete,
delete your own claim file, push. Green then merges server-side; a
flipped-early card merges a partial PR (the failure the gate exists
for), and an unpushed flip leaves the PR red forever.Declared capabilities: edit (the log + docs), run (the checks + git).