compound-engineering

Check or stop the post-work chain (work → review → discover)

Implement discovered patterns into the local project plugin and update subsystem knowledge

Analyze work session to discover reusable patterns and specify appropriate components for the local project plugin

Systematically explore and document a subsystem for the compound engineering knowledge base

Start autonomous engineering loop — pulls issues from Linear, executes plan→work→review→commit cycle

Get context on a Linear project and issue, review previous work, and understand codebase state

Produce a dependency-aware change plan by consulting subsystem knowledge before reading source code

Assemble codebase context for frontier reasoning models and transform their responses into actionable work

Verify completed work against subsystem contracts and tests. Maps changed files to subsystems, checks invariants, runs tests by tier, and identifies spec gaps.

Final wrap-up — verify subsystem spec, set Linear issue to Done with implementation comment, commit task-specific files

Decompose a product vision into a Linear hierarchy (initiative, project, milestones, issues) grounded in subsystem knowledge

Execute planned work while leveraging subsystem knowledge and applying the improvement mindset

This skill should be used when the user invokes "/consolidate", asks to "process discoveries", "implement compound improvements", "review pending patterns", or wants to turn discovered patterns into actual project plugin components and subsystem knowledge updates. Provides methodology for reviewing, approving, and implementing discovery artifacts.

This skill should be used when the user invokes "/discover", asks to "find patterns", "extract workflows", "what could be a skill", "what could be a command", "modularize this", "discover repeatable procedures", or wants to identify engineering patterns that could become new plugin components. Provides methodology for subsystem-aware pattern extraction and component type selection.

This skill should be used when running the autonomous engineering harness (/harness start), when the user asks about "harness gate rules", "autonomous work protocol", "harness failure handling", or when Claude needs guidance on autonomous decision-making during unsupervised plan-work-review-commit cycles.

This skill should be used when starting any significant engineering task, when the user asks to "work with improvement mindset", "apply compound thinking", "set up improvement cycle", or when Claude should proactively apply the improvement lens during /work execution. Provides the active thinking framework to use DURING work, not just after.

This skill should be used when the user wants to "reason about architecture", "get strategic analysis", "use a reasoning model", "prepare context for deep think", "transform reasoning output", or when Claude needs to assemble codebase context for frontier reasoning models and transform their responses into actionable work items.

This skill should be used when the user asks to "reflect on this session", "capture learnings", "what did we learn", "debrief this work", or wants to create a structured learning artifact from recent engineering work. Provides methodology for subsystem-aware reflection and structured output.

This skill should be used when the user wants to "plan a migration", "build feature X", "break down a project", "create a roadmap", "plan this initiative", "what would it take to build X", "decompose this into issues", or when Claude needs to decompose a product vision into a Linear hierarchy (initiative, project, milestones, issues) grounded in subsystem knowledge.