AgentSkillsCN

session-compounding

对一次工作会话的产出进行复盘，识别可改进的模式，分类整理各项优化建议，并优先落实其中最紧迫的改进措施。在重要工作会话结束时使用，以确保执行闭环中的“复合”阶段得以顺利推进。若缺乏明确的复合行动，改进便难以真正落地。

SKILL.md
--- frontmatter
name: session-compounding
description: Reviews a work session's output to detect improvable patterns, classify improvements, and execute the highest-priority one. Use at the end of significant work sessions to ensure the COMPOUND phase of the enforcement loop happens. Without explicit compounding, improvement never happens.
protocol_id: PROTO-ORG-5
protocol_file: organon/protocols/PROTOCOLS.md
tools: [organon-verify, organon-health, organon-find]
loads:
  - CLAUDE.md
  - book-llms/patterns.md
  - book-llms/workflow-authoring.md

Session Compounding Workflow

Implements PROTO-ORG-5 from organon/protocols/PROTOCOLS.md. Converts session learnings into durable improvements.

When to Use This Skill

Use this skill when:

  • •Ending a significant work session — substantial changes were made
  • •After completing a multi-step task — new patterns may have emerged
  • •After encountering friction — something was harder than it should have been
  • •Periodically — even smooth sessions may reveal optimization opportunities

Purpose: The methodology warns: "Without explicit time allocation, improvement never happens." This workflow makes the COMPOUND step actionable.

Context Loading

  1. •Load project constraints:
    • •Read CLAUDE.md (project-level guidance and decision heuristics)
  2. •Load pattern references:
    • •Read book-llms/patterns.md (Recursive Collaboration section — the pattern this workflow implements)
    • •Read book-llms/workflow-authoring.md (workflow quality attributes for evaluating workflow improvements)

Steps

Step 1: Review Session Work

Examine what happened during the session:

bash
git diff --stat HEAD~N  # where N = number of commits in this session
git log --oneline -N    # recent commits

List:

  • •Files created or modified
  • •Types of changes (organon content, tooling, skills, documentation)
  • •Patterns in the work (what was repeated, what was manual)

Step 2: Detect Patterns

Look for these improvement signals:

SignalExampleIndicates
Repeated manual steps"I ran organon validate then organon verify then organon health every time"Tool candidate (composite command)
Unclear workflow"I wasn't sure which skill to use for this task"Workflow gap or unclear naming
New heuristic discovered"I learned that scopes.md always needs updating after ETHOS.md changes"Heuristic addition to CLAUDE.md or ETHOS.md
Awkward tool usage"I had to run the same command 3 different ways to get what I needed"Tool improvement (better defaults, new flag)
Missing context"I needed to read 5 files before starting but the skill only listed 3"Workflow context update
Terminology confusion"I kept saying 'skill' when I meant 'workflow'"Terminology cleanup needed
Error without guidance"The tool failed but I didn't know how to fix it"Error recovery table addition

Step 3: Classify Improvements

For each finding, categorize it:

CategoryDescriptionWhere to Implement
Tool candidateRepeated operation that could be automatedpackages/tools/ — new command or flag
Protocol updateProcedure followed but not documentedorganon/protocols/PROTOCOLS.md — new or updated protocol
Heuristic additionDecision made repeatedly in same wayCLAUDE.md or organon/ETHOS.md — new heuristic row
Workflow refinementExisting workflow that was awkward or incomplete.claude/skills/<name>/SKILL.md — update steps, context, or error recovery
Documentation gapInformation needed but not findablebook-llms/ or book-humans/ — new content

Step 4: Prioritize

Rank improvements by frequency x impact:

code
Priority = How often does this recur? × How much friction does it cause?
FrequencyImpactPriority
Every sessionBlocks workHighest — do now
WeeklySlows workHigh — do this session
MonthlyAnnoyingMedium — create RFC or TODO
RareMinorLow — note for future

Step 5: Generate Improvement Plan

For the top-priority improvement, draft:

  1. •What — specific change to make
  2. •Where — exact file(s) to modify
  3. •Why — what problem this solves
  4. •How to verify — how to confirm the improvement works

Step 6: Execute Improvement

With user confirmation, implement the highest-priority improvement:

  • •If tool candidate → create RFC (use domain-feature-design skill)
  • •If protocol update → edit PROTOCOLS.md
  • •If heuristic addition → edit CLAUDE.md or organon/ETHOS.md
  • •If workflow refinement → edit the skill file
  • •If documentation gap → create or update the relevant file

Step 7: Check for Stale Terminology

Search ALL files for terminology that may have become inconsistent during the session:

Use the Grep tool to search all files for the term:

code
Grep pattern="<term-to-check>" path="." glob="*.md"

Also check organon files by name:

bash
cd packages/tools && npx organon find --name "<term-to-check>"

Check common drift points:

  • •CLAUDE.md vs organon/ETHOS.md (must stay in sync)
  • •Skill descriptions vs actual skill content
  • •Protocol names vs workflow names

Step 8: Run Verification

bash
cd packages/tools && npx organon verify
cd packages/tools && npx organon health

Confirm no regressions from the improvement.

Verification

  • • At least one improvement identified and classified
  • • Highest-priority improvement either executed or documented
  • • organon verify passes after any changes
  • • organon health score has not decreased
  • • No stale terminology found

Error Recovery

FailureRecovery Action
No patterns detectedSession may have been too small or too routine. Note for next session. Consider: was the session too short, or is the workflow already well-optimized?
Improvement breaks verificationRevert the improvement. Re-analyze the approach — the improvement may need a different implementation strategy.
User declines executionDocument the improvement as a TODO comment in the relevant file, or create an RFC for larger improvements.
Too many improvements foundDon't try to do everything. Execute only the highest-priority one. Document the rest for future sessions.
Improvement requires RFCUse domain-feature-design skill to create the RFC. Don't implement without proper design for significant changes.