compound

To document sprint learnings, extract actionable insights from review, security, QA, and ship artifacts. Structure these findings into searchable markdown solution files with tags, severity, and validation metadata to preserve investigative work. This prevents valuable debugging knowledge from being lost in ephemeral artifacts.

The best way to create a post-mortem decision log is to synthesize resolved findings into a markdown solution file. Include root cause, remediation steps, prevention rules, and affected file paths. Apply frontmatter with severity, applied_count, and validation status to ensure the log is searchable and reusable.

Yes, you can extract knowledge from QA and security artifacts by ingesting them post-sprint. The process distills these artifacts into structured solution documents, categorizing them as bug, pattern, or decision files with appropriate tags and metadata for future searchability.

Convert recurring bug patterns into reusable solutions by summarizing captured findings into a compound artifact. Check for graduation candidates to transform high-confidence solutions into SKILLs, ensuring validated patterns are elevated from simple documentation into actionable, automated rules for future sprints.

No dependencies are required to manage sprint artifacts with this knowledge-capture process. It operates independently to read resolved findings and update existing or create new markdown solution files, relying solely on your existing sprint artifacts for input.