land-the-plane

Converts session-end claims into a receipted ledger with evidence, registrations, and handoffs.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill land-the-plane-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-the-plane
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/.warp/skills/land-the-plane
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill land-the-plane-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sessions often end with claims of completed work that were never verified, producing phantom artifacts and narrated-as-done summaries. This Skill audits every completion claim made during a session and binds each one to checkable evidence before the final summary is written. ## Core Features & Use Cases - Claim harvesting and receipt binding: Sweeps the session transcript for every claim of done/fixed/exists/passes and attaches verifiable evidence such as commit hashes, pytest output, file paths, or spine receipt ids. - Structured disposition routing: Routes unreceipted claims to exactly one outcome — REGISTERED in docs/state/BROKEN_REGISTER.md, HANDED OFF with an exact next command, or RETRACTED as a corrected phantom. - Ledger receipt output: Writes a JSON ledger to ~/.dharma/session_ledgers/ and emits a LANDING LEDGER table in the final message that gates what the prose summary may claim. - Use Case: At the end of a coding session where you fixed tests, edited files, and pushed a branch, invoke this Skill to produce a ledger proving each claim with a commit hash or test run, retract anything unverified, and hand off remaining work with runnable next steps. ## Quick Start Tell the agent to land the plane and audit this session's claims into a receipted ledger before writing the final summary.

Frequently Asked Questions about land-the-plane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify claims made during an AI coding session?▼

Harvest every claim of done, fixed, exists, or passes from the session transcript, then bind each to checkable evidence like a commit hash, pytest tail with exit code, or a file path confirmed on disk. Claims without cheap read-only verification are routed to registration, handoff, or retraction.

What is a session-close receipt ledger?▼

It is a structured record where every session claim is marked RECEIPTED, REGISTERED, HANDED_OFF, or RETRACTED with supporting evidence. The ledger is emitted as a table in the final message and stored as JSON under ~/.dharma/session_ledgers/ so a stranger with repo access can verify each row.

When should I use land-the-plane in a workflow?▼

Use it at the end of any working session, or when the operator says land it, wrap up, or close out. It runs as the last step before the final summary, gating what the prose may claim based on what the ledger receipted.

Can the skill run builds or new work to verify claims at session close?▼

No. Only cheap read-only checks like git log, targeted pytest, or ls on cited paths are allowed at close. Claims requiring expensive verification are handed off with an exact next command rather than laundered into receipts through new build work.

What happens to claims that turn out to be false?▼

False or phantom claims are retracted, meaning the summary text itself is corrected to state the thing did not happen. Phantoms are never softened into handoffs, and retractions are logged as findings in the ledger.