ce-compound

Document recently solved bug fixes by running parallel research subagents to capture context, root cause, and prevention strategies, then assemble the validated outputs into a single canonical markdown file. This prevents knowledge loss while the resolution is still fresh.

Automating post-mortem documentation involves orchestrating subagents to extract working solutions, generate prevention strategies, and validate YAML frontmatter. It enforces a single final write to a canonical markdown file to ensure a structured, searchable knowledge base entry.

Yes, you can run multiple subagents in parallel to analyze context, find related documentation, and classify the category. The collected text outputs are validated and assembled into one markdown solution file under a structured docs directory.

Yes, the post-incident workflow supports optional specialized review agent invocations. After the canonical markdown document is written, you can trigger specialized reviewers for performance, security, database, and code quality to enrich and validate the content.

Enforce a single source of truth by validating collected text outputs and YAML frontmatter, then restricting the final write to one specific file path in the docs/solutions directory. This prevents fragmented documentation across cross-team investigations.

The post-incident knowledge base entry uses a single canonical markdown file with validated YAML frontmatter. This structured format ensures the captured context, root cause, fixes, and cross-references remain searchable and consistent.