compound-engineering_skill

This skill guides AI-assisted development using the Plan → Work → Review → Compound loop to make future work easier.

380

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill snarktank/amp-skills --skill compound-engineering

  • SKILL.md8.0 KB

Overview

This skill implements the Compound Engineering workflow for AI-assisted development. It guides teams through a Plan → Work → Review → Compound loop so each unit of engineering makes subsequent work easier. Use it to plan features, execute code, run reviews, and codify learnings so knowledge compounds across the codebase.

How this skill works

The skill inspects the codebase, commit history, and documentation to produce a detailed implementation plan tailored to existing patterns. During execution it enforces systematic work: isolated branches, incremental commits, and continuous validation. The review step runs a checklist for quality, security, performance, and tests. Finally it generates concrete artifacts (patterns, decisions, lessons) and updates project guidance so future work is faster and safer.

When to use it

  • Planning a new feature that should follow existing patterns
  • Implementing a change where long-term maintainability matters
  • Reviewing pull requests to ensure consistency and robust tests
  • Codifying post-mortems, decisions, and patterns for future contributors
  • Creating acceptance criteria and testing strategies before coding

Best practices

  • Invest 60–80% effort in planning and review; execution should be disciplined and incremental
  • Search codebase and git history for priors before inventing new patterns
  • Keep commits small, focused, and accompanied by clear messages and tests
  • Prefer simple duplication over premature abstraction; document any new abstraction with rationale
  • Turn every bug or design choice into a documented lesson, test, or AGENTS.md entry

Example use cases

  • Generate a comprehensive plan for a multi-day feature with acceptance criteria and risks
  • Run a pre-merge review checklist on a PR and produce an actionable feedback list
  • Execute a plan: create a feature branch, break tasks into TODOs, and validate after each change
  • Compound learnings after a bug fix: write a lesson, add a regression test, and update subsystem AGENTS.md
  • Convert architectural decisions from a design discussion into a Decision artifact with trade-offs

FAQ

Plan documents with acceptance criteria and technical approach, incremental commits/tests, review checklists, and compound artifacts (patterns, decisions, lessons) placed in AGENTS.md or subdirectory guidance.

How does this reduce technical debt?

By prioritizing research and review, documenting choices, and converting failures into tests and guidance, future work reuses proven patterns and avoids repeating mistakes, lowering cumulative debt over time.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
compound-engineering skill by snarktank/amp-skills | VeilStrat