Files

Paul O'Reilly f41c22d0ac Add question-reframing guidance to CLAUDE.md; commit accumulated project files

- CLAUDE.md: add "Question the question" and "One clarifying question" rules
  to Tone and Interaction — XY problem detection, false premise checks, and
  explicit reframe pattern before answering
- Add claude/ detail-file directory (topic docs referenced from CLAUDE.md)
- Add ABOUT.md, FUTURE.md
- Update memory/, scripts/, settings.yaml with accumulated session changes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-25 09:37:28 +12:00

1.8 KiB

Raw Blame History

skill: /end-session

Location: custom-claude-skills/skills/end-session/SKILL.md

Purpose

End-of-session wrap-up that combines session logging, CONTEXT.md update, and project doc refresh into a single command. Replaces the manual workflow of running /log then separately updating CONTEXT.md and project docs.

Usage

/end-session

No arguments. Reviews the full conversation history automatically.

How it works

Session log (Phase 1): Creates memory/log/YYYY-MM-DD.<HHMMSS>.md with structured entries (Summary, Decisions, Gotchas, Open Questions, Key Context, Process Notes). Prunes old reflected logs per retention settings.
Context update (Phase 2): Assesses what's in progress, updates CONTEXT.md index and context/<topic>.md detail files so the next session can resume without conversation history.
Doc refresh (Phase 3): Updates FUTURE.md (new ideas), README.md (milestone table, scripts section), and CLAUDE.md (repo structure, conventions) -- only where this session actually changed something.
Summary (Phase 4): Prints what was logged, what the next session should pick up, and which docs were updated.

Relationship to other skills

Subsumes /log -- no need to run /log separately when using /end-session
Does NOT include milestone reflection -- use /reflect M<N> separately when a milestone is complete
CONTEXT.md updates follow the same thin-index pattern documented in CLAUDE.md

Gotchas

Pre-gathers git log, git status, MEMORY.md, CONTEXT.md, FUTURE.md at skill load time -- if you made changes after invoking the skill, the pre-gathered data may be stale (but the skill can re-read files via tool calls)
[topic] tags on gotchas should match existing memory file topics for routing by /reflect-logs

1.8 KiB Raw Blame History