# Session Notes Skill — Session Notes

Session log for the session-notes-skill project. Each session is a dated
heading with a list of changes. Each change has a label, narrative, and
four structured fields (What, Why, How, Touches).

---

## Session — 2026-04-27

### SKILL.md Definition
Wrote the core skill definition with trigger description, format template,
granularity rule, and writing quality guidance. The trigger is set to fire
automatically at the end of any coding session where files changed, and
also responds to manual invocations like "write session notes" or "wrap up."

- **What:** SKILL.md with session notes convention and auto-trigger
- **Why:** Need a reusable skill that enforces consistent session documentation
  across all projects and all Claude Code sessions
- **How:** YAML frontmatter with pushy description for reliable triggering.
  Body covers when/where/format/granularity. Includes good-vs-bad granularity
  comparison and file header template for new projects.
- **Touches:** session-notes/SKILL.md (new)

### Reference Examples
Created a reference file with four real session entries from the Loom
project (work-index-dashboard) showing the correct granularity and style.
Covers different change types: new function, scanner utility, security fix,
and config setup.

- **What:** Example session entries for agent calibration
- **Why:** The granularity rule needs concrete examples to be effective —
  abstract rules alone lead to over-summarization
- **How:** Extracted and lightly edited four entries from the Loom session
  notes that were validated as "right granularity" by Travis.
- **Touches:** session-notes/references/example-session.md (new)

### Project Documentation
Added CLAUDE.md with key patterns section documenting the skill-as-convention
approach, granularity rule importance, progressive disclosure pattern, and
the separation between skill (convention) and session data (in each project).

- **What:** CLAUDE.md with architecture and key patterns
- **Why:** Future sessions working on this skill need to understand the
  design decisions, not just the file tree
- **How:** Follows the review-ready CLAUDE.md convention established in the
  Loom project — file tree plus key patterns plus session notes pointer.
- **Touches:** CLAUDE.md (new)