AgentSkillsCN

session-documenter

以明确的指令记录会话工作。使用 /start 开始追踪,/end 结束会话,/clear 重置会话。全程记录决策过程、文件变更,以及上下文信息,确保工作连续性。

SKILL.md
--- frontmatter
name: session-documenter
description: 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.
triggers:
  - /start
  - /end
  - session start
  - session end
  - document session
  - what did we do
  - track this decision

Session Documenter Skill

Document work, decisions, and context with explicit commands.

Commands

CommandAction
/startBegin new session - creates/appends to today's file, loads context
/endFinalize session - writes entry with all tracked work, updates related files

How It Works

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

Critical Rules

Session File Naming (ONE FILE PER DAY)

code
✅ 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

  1. Session number and title
  2. System flow diagram (mermaid or text)
  3. Affected components (frontend, backend, data, external)
  4. What was done (task checklist)
  5. Key decisions (with rationale)
  6. Files changed
  7. Mistakes and fixes
  8. 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