session-documenter

Original：🇺🇸 English

Translated

Document session work with explicit commands. Use /start to begin tracking, /end to finalize session, /clear to reset. Tracks decisions, file changes, and context for continuity.

1installs

Sourceshipshitdev/library

Added on2026-02-04

NPX Install

npx skill4agent add shipshitdev/library session-documenter

SKILL.md Content

View Translation Comparison →

Session Documenter Skill

Document work, decisions, and context with explicit commands.

Commands

Command	Action
`/start`	Begin new session - creates/appends to today's file, loads context
`/end`	Finalize session - writes entry with all tracked work, updates related files

How It Works

/start
- Creates
```
.agents/SESSIONS/YYYY-MM-DD.md
```
if missing, or loads existing context
During session - You tell me what to track: decisions, files changed, mistakes
/end
- I write the full session entry with flowcharts, decisions, next steps

Critical Rules

Session File Naming (ONE FILE PER DAY)

✅ CORRECT: .agents/SESSIONS/2025-11-15.md
❌ WRONG:   .agents/SESSIONS/2025-11-15-feature-name.md

Multiple sessions same day → Same file, Session 1, Session 2, etc.

Flowcharts (MANDATORY for features)

Include flowchart for:

New features
Feature modifications
Multi-component bug fixes

Session Entry Structure

Session number and title
System flow diagram (mermaid or text)
Affected components (frontend, backend, data, external)
What was done (task checklist)
Key decisions (with rationale)
Files changed
Mistakes and fixes
Next steps

Related Files to Update

```
.agents/SESSIONS/README.md
```
```
.agents/SYSTEM/SUMMARY.md
```
```
.agents/TASKS/*/TODO.md
```
```
.agents/SYSTEM/ARCHITECTURE.md
```
(if architectural decisions)

References

Full guide: Phases, automation, validation, examples