compound-docs

Document solved problems into docs/solutions with searchable tags and validated YAML frontmatter.

47|7|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/salavender/antigravity-compound-engineering-plugin --skill compound-docs-salavender
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/salavender/antigravity-compound-engineering-plugin/tree/main/skills/compound-docs
Command: npx skills add https://github.com/salavender/antigravity-compound-engineering-plugin --skill compound-docs-salavender

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document solved problems for knowledge persistence across sessions.

Core Features & Use Cases

  • Document solutions to docs/solutions for reuse
  • Find existing solutions through searches
  • Promote recurring issues to patterns
  • Validate YAML frontmatter to ensure schema compliance

Quick Start

Document a solved problem by adding a new entry to docs/solutions using the compound-docs workflow.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I document solved problems for knowledge persistence across sessions?

Document solved problems for knowledge persistence by adding entries to docs/solutions, capturing context and outcomes, and validating YAML frontmatter against schemas to ensure future searchability and reuse.

What is the best way to find existing solutions to recurring issues in a knowledge base?

Find existing solutions in a knowledge base by searching docs/solutions using searchable tags, allowing teams to locate documented context, outcomes, and patterns from previously resolved issues.

How do I validate YAML frontmatter to ensure schema compliance for documentation?

Validate YAML frontmatter to ensure schema compliance by checking that documentation entries in docs/solutions satisfy frontmatter schemas before persisting them to the knowledge base.

When should I promote recurring issues to patterns in a knowledge base?

Promote recurring issues to patterns when documented solutions in docs/solutions show repeated context and outcomes, transforming them into reusable workflows for future sessions and teams.

Can I use a documentation workflow to capture solving journeys across multiple teams?

Capture solving journeys across multiple teams by applying a documentation workflow that records context, outcomes, and patterns into docs/solutions, ensuring knowledge persistence and future reuse.