session-log

name	session-log
description	Create or update a session log to capture decisions, changes, and progress.

Session Log

Create or update a session log to capture decisions, changes, and progress.

Input: $ARGUMENTS — create for a new log, update to append to the most recent log, or a short description of what to log.

---

Step 1: Determine Mode

• If $ARGUMENTS is create, or no session log exists in quality_reports/session_logs/ -> Create mode
• Otherwise -> Update mode

---

Step 2: Create Mode

1. Read the most recent plan from quality_reports/plans/ if one exists.
2. Inspect recent commits with git log --oneline -10.
3. Use the session-log template resolution rule below to find the format template.
4. Create quality_reports/session_logs/ if it is missing before saving.
5. Save to quality_reports/session_logs/YYYY-MM-DD_short-description.md.
6. Populate:
   • Objective: from the plan or $ARGUMENTS
   • Status: IN PROGRESS
   • Design Decisions: each one prefixed with Decision:
   • Changes Made: a short starting summary based on the plan or recent git activity

Tell the user where the log was created.

---

Step 3: Update Mode

1. Read the most recent session log in quality_reports/session_logs/.
2. Inspect git diff --stat and git log --oneline -5.
3. Append new information to the appropriate sections:
   • Changes Made: newly modified files or major milestones
   • Design Decisions: add any new decisions as Decision: [text]
   • Incremental Work Log: add a timestamped entry for the current work
4. If the planned work is complete, update Status to COMPLETED.

Tell the user what was added or updated.

---

Template Resolution

For session-log.md, resolve templates in this order:

1. plugins/social-science-research/templates/session-log.md in repo-scoped installs
2. templates/session-log.md when working inside the plugin repo
3. Fall back to the embedded format implied by this skill if neither file exists

---

Key Rules

• Keep the log factual. Capture what changed and why, not aspirational notes that did not happen.
• Prefix decisions consistently. Use Decision: so hooks and recovery workflows can parse them later.
• Prefer updating the latest relevant log instead of creating duplicates for the same workstream.