Sop Session Audit

Use this skill when writing a session audit file. Triggers: creating audit, writing to .claude/audits/, documenting session work, capturing design decisions, recording feedback from user.

machow Updated

File contents

Session Audit SOP

Goal

Capture what matters from a session:

  • What we did - changes made, files modified
  • Key decisions - choices and their rationale
  • Important feedback - user corrections that shaped the work
  • Patterns to remember - lessons for future sessions

Procedure

  1. Name the file with date: .claude/audits/YYYY-MM-DD-feature-name.md

    /bin/date +%Y-%m-%d  # get current date
    
  2. Write audit following template: See TEMPLATE.md

  3. Ensure feedback captures conversation flow - not just the end result, but the progression of corrections

  4. If no feedback recorded, think carefully - most sessions have at least some course corrections worth noting

  5. Summarize to user after writing: Report back with:

    • Audit file name
    • Key feedback points (quote the "Important Feedback" section)
    • Patterns learned (list from "Patterns to Remember")

    This ensures the user sees what was captured without having to open the file.

Note: Audit files are gitignored - don't commit them.

machow/dev-skills/tree/main/sop-session-audit commit 1c1e31102e

Frequently asked questions

npx skillmds@latest add machow/sop-session-audit