Claude Code '/land' skill — interrogate your session before closing out. Extracts decisions, surprises, patterns, and loose ends so nothing valuable evaporates when you /clear.

land.md

Landing the plane — interrogate this session before closing out.

Purpose

Extract maximum value from the current session by grilling me with targeted questions about what happened, what I learned, and what should be remembered. This is the closing loop — nothing valuable should evaporate when I /clear.

Steps

1. Scan what happened: Review the conversation context — what was the goal, what changed, what decisions were made, what was discovered. Run git diff --stat to see the actual code changes from this session.

2. Generate 3-5 targeted questions: Based on what happened, generate probing questions. These should NOT be generic — they should be specific to this session's work. Categories to consider:

   • Decisions: "You chose X over Y — what drove that? Will this hold up?"
   • Surprises: "What was unexpected about how [specific thing] worked?"
   • Patterns: "You touched [files/areas] — did you notice any patterns or tech debt worth noting?"
   • Gaps: "Is there anything you started but didn't finish? Anything that felt fragile?"
   • Future self: "If you come back to this code in 3 months, what would you want to know?"
   • Documentation: "Should CLAUDE.md, memory files, or any docs be updated based on this work?"

3. Ask questions one at a time: Present each question, wait for my answer. If I say "skip", move on. If I give a brief answer, that's fine — don't push for more.

4. Capture valuable answers: For each substantive answer:

   • If capture_note MCP tool is available (Second Brain connected): use it with tags ["session-landing", "debrief"] plus topic-specific tags. Content should be self-contained.
   • Otherwise: save insights to the project's auto-memory files (.claude/projects/.../memory/) so they persist across sessions.

5. Check for loose ends:

   • Run git status — flag any uncommitted changes
   • Check if there are action items that should be created from our conversation
   • If I mentioned wanting to remember something, suggest saving it to memory

6. Wrap up: Brief summary of what was captured. Don't over-summarize — just confirm what notes were saved and any flags.

Rules

• Be direct and specific — no softball questions. The point is to extract non-obvious value.
• Don't ask more than 5 questions. Respect my time.
• If the session was trivial (quick fix, simple question), say so and skip the interrogation. Not every session needs landing.
• Don't repeat things I already said during the session — dig for what WASN'T said.
• If nothing worth capturing comes up, that's fine — say "clean landing" and move on.