session-compounding

Review work session outputs to classify and execute prioritized improvements.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/VledicFranco/organon --skill session-compounding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-compounding
Source: https://github.com/VledicFranco/organon/tree/main/.claude/skills/session-compounding
Command: npx skills add https://github.com/VledicFranco/organon --skill session-compounding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a work session's output to detect improvable patterns, classify improvements, and execute the highest-priority one to ensure the COMPOUND phase of the enforcement loop happens.

Core Features & Use Cases

  • Detect recurring friction and transform learnings into actionable improvements.
  • Classify improvements by impact and feasibility to drive a prioritized plan.
  • Execute and document improvements, updating related guidance and workflows.

Quick Start

Run this skill at the end of a significant work session to generate and execute the highest-priority improvement from observed patterns.

Frequently Asked Questions about session-compounding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn session observations into durable workflow improvements?

To turn session observations into durable workflow improvements, you review work session outputs to detect recurring friction, classify improvements by impact and feasibility, and execute the highest-priority change to update protocols. This enforces a continuous compounding phase for execution.

What is the best way to prioritize execution improvements after a work session?

The best way to prioritize execution improvements is to analyze detected patterns from your session outputs and classify each potential improvement by its impact and feasibility, generating a prioritized plan that drives immediate execution and workflow updates.

How do I detect recurring friction patterns from my work outputs?

You detect recurring friction patterns by reviewing work session outputs and observations to identify improvable areas, analyzing these patterns to classify potential improvements, and documenting actionable observations for future workflow refinement.

When should I run a session review to generate a prioritized improvement plan?

You should run a session review at the end of a significant work session to ensure the compounding phase happens, detecting improvable patterns and executing the highest-priority improvement before finalizing your workflow updates.

Does this approach require specific dependencies to update workflows and protocols?

No dependencies are required to update workflows and protocols. The skill operates independently to analyze session outputs, classify improvements, and enforce guidance updates by modifying workflows, protocols, or skill steps as needed.

What limitations exist when classifying improvements by impact and feasibility?

A key limitation is that classifying improvements relies entirely on the quality of your session observations and outputs. Without detailed observations of recurring friction, the prioritized plan may lack actionable depth for updating workflows or protocols.