Session Intelligence Harvester FAQs

Question 1

When should I use this skill in my workflow?

Accepted Answer

Trigger this skill whenever you've corrected a recurring error, fixed format drift, or established a new architectural pattern. You can also manually invoke it with commands like 'harvest learnings' or 'capture session intelligence' to perform a systematic audit of your recent work.

Question 2

How does it improve future AI interactions?

Accepted Answer

It prevents 'session amnesia' by encoding context into your Reusable Intelligence Infrastructure (RII). By updating CLAUDE.md and agent-specific convergence patterns, you ensure that future Claude sessions proactively avoid the same failure modes you've already solved.

Question 3

What specific files can this skill update?

Accepted Answer

The Harvester is designed to route intelligence to CLAUDE.md (for context gathering and failure modes), agent-specific markdown files (for convergence patterns and checklists), skill definitions, and orchestration command files for Phase 0 validation checks.

Question 4

What does the Session Intelligence Harvester skill do?

Accepted Answer

This skill acts as a bridge between active coding sessions and long-term memory. It analyzes corrections, discoveries, and pattern changes made during a session and automatically routes those learnings into your documentation, agent files, and system protocols to ensure they are never forgotten.

Question 5

Does this skill automate the implementation of updates?

Accepted Answer

Yes. Unlike simple logging tools, the Session Intelligence Harvester defaults to action. It reads your target RII files, generates precise edits based on session analysis, implements the changes using the Edit tool, and creates a Progress History Record (PHR) for your commit history.

Session Intelligence Harvester

Session Intelligence Harvester

Key Features

Use Cases

Key Features

Use Cases