claude-sdk-rs: Command for Claude Code

Session Recap — Summarize recent work and current standing before starting a session.

Reads the most recent Log entries and status.md to produce a tight briefing: what was completed recently, where work left off, and the exact next command to run. Use this at the start of a coding session before doing anything else.

Instructions

1. Check for an active handoff: ls planning/handoff.md 2>/dev/null.

   • If the file exists, read it and lead the briefing with an Active Handoff section:

     ## Active Handoff — <title from handoff.md>
     <What's in flight and why.>
     Remaining: <bullet list from "Remaining work">
     First command: `<command from "First command after /prime">`
     > Delete `planning/handoff.md` once this session has consumed it.
     

   • If absent, skip silently and proceed to step 1.

2. Read log.md. Focus on the three most recent entries (identified by ## YYYY-MM-DD headings). Extract: what was built or changed, any decisions made, and any explicit "left off at" or "next step" notes the author wrote.

3. Read planning/status.md. Extract:

   • Current focus block
   • Which blocks are In progress, Done, and Not started (status is title-case in status.md; tolerate lowercase variants if present)
   • Last updated date

4. If a task spec exists for the current focus block at planning/<name>/tasks.md, read it. Identify:

   • Which steps are marked done (have [done] prefix)
   • Which steps remain
   • Any notes in the ## Notes section

5. Check planning/<name>/sdlc/reports/ for any existing pipeline reports for the current block (e.g. implement.md, task3-test.md). Note which pipeline steps have been completed (have a report file) and which haven't.

6. Read planning/state.json if present. Extract any active carryover[] entries (those whose clears_when is unresolved) — durable constraints, known-issues, env caveats, and deferred follow-ons. Skip silently if the file or array is absent.