compound-engineering

Analyze errors, stack traces, and logs to identify root causes and recommend fixes

Enhance a plan with parallel research agents for each section to add depth, best practices, and implementation details

Generate comprehensive tests for specified files or features following project conventions

Have multiple specialized agents review a plan in parallel

Triage and categorize findings for the CLI todo system

Researches and synthesizes external best practices, official documentation, community standards, and open-source examples for any technology, framework, or development practice.

Gathers comprehensive documentation and best practices for frameworks, libraries, and dependencies including version-specific constraints and implementation patterns.

Analyzes git history to understand code evolution, trace origins of patterns, identify key contributors, and extract insights from commit history and blame data.

Searches .claude/solutions/ for institutional knowledge, patterns, and solved problems relevant to the current task using grep-first filtering.

Conducts thorough research on repository structure, documentation, architecture, conventions, templates, and implementation patterns to understand project best practices.

This skill provides patterns for safe, systematic refactoring including extract, rename, move, and simplification operations with proper testing and rollback strategies.

This skill should be used when clarifying WHAT to build before HOW, triggered by ambiguous requests or when the user wants to explore requirements and approaches collaboratively.

Capture solved problems as categorized documentation with YAML frontmatter for fast lookup

This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.

This skill should be used when analyzing errors, stack traces, and logs to identify root causes and implement fixes.