compound

Convert session friction into durable process improvements after completed work units.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/mslshao/claude-harness --skill compound-mslshao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound
Source: https://github.com/mslshao/claude-harness/tree/main/dotclaude/skills/compound
Command: npx skills add https://github.com/mslshao/claude-harness --skill compound-mslshao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn the friction from a just-finished work session into concrete improvements instead of letting useful lessons disappear. It is designed for cases where work shipped successfully, but the session still exposed preventable inefficiencies like tool retries, repeated edits, manual verification steps, or missing guidance.

Core Features & Use Cases

  • Friction-based improvement detection: Scans recent work for grounded signals such as blocked tool calls, redo edits, unnecessary confirmation loops, and manual cross-referencing.
  • Dedup and routing: Checks whether the pattern is already covered in memories, workflow notes, rules, or skills, then routes the improvement to the right durable surface.
  • Build-first workflow: Proposes a specific edit to a hook, skill, memory file, or related artifact, with explicit user approval before anything is written.
  • Fallback capture: If no concrete buildable fix exists, it records the softer pattern as habit memory so it can be promoted later if it repeats.
  • Use case: After a PR merge or a completed investigation, use this Skill to identify what slowed the session down and convert that into a reusable automation, rule, or skill enhancement.

Quick Start

Ask the AI to run the compound skill after a completed work unit and identify buildable improvements from the session friction.

Frequently Asked Questions about compound

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

FAQPage Schema
How do I turn session friction into durable workflow improvements after a PR merge?

To turn session friction into durable workflow improvements, scan completed work for tool retries, redo edits, and manual verification loops, then convert those signals into specific edits for hooks, rules, or memory files with explicit approval before writing.

What is the best way to automate postmortem analysis after completing a complex investigation?

Postmortem analysis automation works by detecting observable friction like blocked tool calls and repeated confirmation loops from a finished session, deduplicating findings against existing memories, and routing the concrete fix to the correct artifact surface.

How do I deduplicate newly identified workflow improvements against existing memory rules?

Deduplication of workflow improvements against existing memory rules involves scanning recent session friction, comparing detected patterns against current memories and workflow notes, and routing only novel, buildable fixes to the appropriate durable artifact surface.

How do I capture soft workflow patterns when no concrete buildable fix exists?

When no concrete buildable fix exists for session friction, capture the softer pattern by recording it as habit memory, allowing it to be promoted into a durable rule or skill enhancement later if the same friction repeats in future work units.

When should I run a session analysis to extract preventable inefficiencies from my code?

Run session analysis to extract preventable inefficiencies after substantial completions like PR merges, launches, or investigations, specifically targeting work units where blocked tools, redo edits, manual user actions, or repeated confirmation loops appeared.

Does skill routing require explicit user approval before writing to memory files?

Yes, skill routing requires a present-and-confirm gate where the system proposes a specific edit to a hook, memory file, or related artifact, and explicit user approval must be granted before any durable write is executed.