Add pre-compact hook to auto-trigger /compound workflow

Open
#95 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #250 by @mvanhorn — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

Start by reading plugins/compound-engineering/commands/workflows/compound.md, especially the existing auto-invoke triggers noted in the issue. Then investigate how the plugin registers hooks that run before context compaction or session end. Done means compoundable sessions are detected, user preferences control prompting or auto-run, trivial sessions are skipped, and the existing command is invoked correctly.

Written by the indexing model from the issue text.

Description

enhancement

Feature Request

Add a hook that triggers before context compaction (or session end) to check if there's anything worth compounding, and if so, automatically run the /workflows:compound command.

Motivation

The /workflows:compound command captures valuable knowledge - solved problems, learnings, patterns discovered - but requires manual invocation. By the time you think to run it, the context may have already been compacted or the session ended, losing that valuable context.

A pre-compact hook would ensure knowledge gets captured at the optimal moment - when the full context is still available and fresh.

Proposed Behavior

  1. Trigger: Before context compaction or session end
  2. Check: Analyze the session for compoundable content:
    • Problems that were solved
    • Significant debugging sessions
    • Pattern discoveries or learnings
    • Non-trivial fixes with root cause analysis
  3. Action: If compoundable content is detected, prompt to run /workflows:compound (or auto-run based on user preference)

Acceptance Criteria

  • Hook triggers before context compaction
  • Intelligently detects if session contains compoundable material
  • Respects user preference (prompt vs auto-run)
  • Doesn't trigger for trivial sessions (simple Q&A, quick fixes)
  • Works with the existing /workflows:compound command

Context

Discussed in the Every Discord. This aligns with the core plugin philosophy: "Each unit of engineering work should make subsequent units of work easier—not harder."

Currently, the /workflows:compound command has auto-invoke trigger phrases like "that worked" and "it's fixed", but a pre-compact hook would provide a safety net for capturing knowledge before context is lost.

Related

  • /workflows:compound command: plugins/compound-engineering/commands/workflows/compound.md
  • Existing auto-invoke triggers (lines 166-169 in compound.md)
Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.