RAD_framework: Skill for Codex

Session Wrap-Up

Capture what happened so the next session starts clean. No project-specific files — this works on any RAD project.

Steps

1. Gather session changes

git branch --show-current
git log --oneline @{u}.. 2>/dev/null || git log --oneline -10
git status --short

Collect the commits made this session, the current branch, and any uncommitted changes.

2. Plan status

rad deliver sets plan status — wrap records notes only and never edits Status:.

3. Append a dated progress note

If meaningful work happened on a plan but its status didn't change, append a dated line to the plan's ## Notes section (create the section if absent) so the next session has continuity:

- {date}: {one-line summary of what was done and what's next}

4. Reconcile plan vs. actual (delivery sessions only)

If on a rad/ branch with an execution log under .agents/logs/, produce a brief reconciliation note. Skip silently if there's no log.

# Find the execution log for this feature
ls .agents/logs/[feature-name]-*.md 2>/dev/null | tail -1

Check three things:

ACs covered: For each numbered AC in the plan, was it cited in a completed task commit? Note any that were deferred or skipped.

Concerns flagged: Were any tasks marked done_with_concerns? List each concern one-line so the architect sees them in the session summary without digging into the log.

Deferred items: Anything in ## Non-Goals or the wave plan that was explicitly left for a follow-up? Name it so the next session has a standing start.

Append this as a ## Session Notes block to the plan doc (create the section if absent):

## Session Notes

- {date}: Delivered Wave [N]. ACs covered: [list]. Concerns: [list or none].
  Deferred: [list or none].

4a. Publish the notes

If Step 3 or Step 4 changed the plan doc, publish it from the rad/ work branch: