agent-method 1.5.1 → 1.5.3

package/templates/starter/SESSION-LOG.md

@@ -1,8 +1,9 @@
 # Session Log
 
-Append-only session observation log for case study data collection. Each session adds a micro-entry at close. This file is read-only during extraction (never during normal work).
+Append-only session observation log for case study data collection. Each session adds a metrics entry at close. High-effort tasks log immediately at task completion. This file is read-only during extraction (never during normal work).
 
-<!-- AGENT INSTRUCTION: At the end of every session, append a new entry below using this format.
+<!-- AGENT INSTRUCTION: At the end of every session — or immediately after any high-effort task —
+     append a new entry below using the format in "Entry format".
      Do NOT read this file during normal work — only append to it.
      Do NOT modify or delete previous entries.
      When this file exceeds 300 lines, archive older entries to session-log/batch-{N}.md -->
@@ -17,9 +18,31 @@ Append-only session observation log for case study data collection. Each session
 | Extension(s) | {code-project / data-exploration / analytical-system / none} |
 | Observation started | {date} |
 
+## Effort classification
+
+| Effort | Description | When to log |
+|--------|-------------|-------------|
+| **low** | Quick answer, single file or no changes, <5 min | At session close |
+| **medium** | Multi-step work, several file changes, 5-30 min | At session close |
+| **high** | Complex multi-file changes, architecture decisions, extensive debugging, 30+ min | Immediately at task completion |
+
+## Assessment scales
+
+**Ambiguity** (agent-assessed — how clear was the user's request?):
+- **low**: Clear, specific request with sufficient context
+- **medium**: Request understood but required interpretation or assumptions
+- **high**: Vague or ambiguous, required significant clarification
+
+**Context level** (agent-assessed — how much project context was loaded?):
+- **very low**: No project files loaded, answered from general knowledge
+- **low**: Entry point only
+- **medium**: Entry point + STATE.md + 1-2 project files
+- **high**: Entry point + STATE.md + specialist context + multiple project files
+- **very high**: Extensive project context, multiple specialists, cross-file analysis
+
 ## Observation checklist
 
-At session close, reflect on these before writing the micro-entry:
+At session close (or high-effort task completion), reflect on these before writing the entry:
 1. Which workflow did this session follow?
 2. Which query types were encountered?
 3. Which features visibly activated? (context loading, cascade, decision recording, scoping)
@@ -27,15 +50,24 @@ At session close, reflect on these before writing the micro-entry:
 5. Were any decisions deferred instead of recorded immediately?
 6. Was there friction with any methodology rule?
 7. Any degradation signals? (HAI-05: cascade misses, instruction loss, shallow context)
+8. How much effort did this task require? (low / medium / high)
+9. How ambiguous was the user's request? (low / medium / high)
+10. How much project context was loaded? (very low / low / medium / high / very high)
+11. Approximate token usage and time spent?
 
-## Session entries
+## Entry format
 
-<!-- Append new entries below. Format:
+<!-- Append new entries below. Format: -->
+<!--
 ### S{N} — {YYYY-MM-DD} — {brief title}
 Model: {model} | Profile: {profile} | Workflow: {WF-XX}
+Effort: {low / medium / high} | Ambiguity: {low / medium / high} | Context: {very low / low / medium / high / very high}
+Tokens: ~{N}k | Time: ~{N} min
 Queries: {query types encountered}
 Features: {feature IDs activated}
 Cascades: {triggered}/{expected} | Decisions: {count}
 Friction: {none | brief description}
 Finding: {none | observation with methodology implication}
 -->
+
+## Session entries