se-compound

Capture solved problems into searchable knowledge docs with YAML frontmatter.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-compound
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-compound
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-compound
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-compound

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Document a recently solved problem to compound your team's knowledge by turning insights into reusable knowledge artifacts.

Core Features & Use Cases

  • Coordinates multiple subagents to capture, structure, and store solutions in docs/solutions with YAML frontmatter for searchability.
  • Produces durable knowledge docs that speed future debugging and feature work.
  • Supports retrospectives and post-mortems by preserving reasoning and context for cross-project reuse.

Quick Start

Create a concise knowledge doc describing the latest fix, including the problem, root cause, and implemented solution.

Frequently Asked Questions about se-compound

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

FAQPage Schema
How do I document solved software engineering problems for future team reference?

To document solved software engineering problems, you can structure the issue, root cause, and solution into a searchable knowledge artifact using YAML frontmatter. This captures reasoning and context for cross-project reuse.

What is the best way to structure post-mortems and retrospectives for searchability?

The best way to structure post-mortems for searchability is to store them as knowledge docs in a dedicated directory with YAML frontmatter. This preserves debugging reasoning and enables future discovery.

How do subagents help build a knowledge management system for software solutions?

Subagents help build a knowledge management system by coordinating to capture, structure, and store software solutions. They generate durable knowledge docs with metadata to speed future feature work.

Can I use YAML frontmatter to categorize fixed bugs by problem type?

Yes, you can use YAML frontmatter to categorize fixed bugs by problem type. The system derives the category from the problem type and outputs metadata to enable reuse in future debugging scenarios.

What should I include in a knowledge doc to make it useful for future debugging?

A knowledge doc should include the problem description, root cause, and implemented solution. This concise content forms a durable knowledge artifact that speeds up future debugging and feature work.