Convert failures and review findings into reusable guardrails and lessons.
npx skills add https://github.com/Sailfishc/guanfu --skill gf-compound
Please help me install this Agent Skill. Skill: gf-compound Source: https://github.com/Sailfishc/guanfu/tree/main/skills/gf-compound Command: npx skills add https://github.com/Sailfishc/guanfu --skill gf-compound
Turn failures, review findings, taste mismatches, and process surprises into reusable project memory. A compound note should change future behavior. It must name the guardrail or explain why a guardrail is unnecessary.
Create a new compound note capturing the failure, the guardrail decision, and the next steps to evolve the skill.
High-intent search queries and answers about installing and using this skill.
You convert incidents into reusable project knowledge by capturing root cause and evidence, then producing a compound note that either names a specific guardrail or explains why one is unnecessary to change future behavior.
A compound note in knowledge management is a record that transforms failures, review findings, and taste mismatches into reusable project memory. It must change future behavior by establishing a guardrail or justifying why one is not needed.
Document root cause analysis results for code reviews by capturing the failure and evidence in a compound note, which updates the compound index and routes the issue to process evolution when gaps exist or the issue recurs.
Yes, you can use this approach for process audits and taste mismatches. It transforms process surprises and taste mismatches into actionable guardrails and lessons, updating the index to route recurring issues toward process evolution.
You should create a compound note instead of just fixing the code when a failure reveals a process gap, taste mismatch, or review finding that needs a documented guardrail to prevent recurrence and drive future process improvement.
The best way to capture guardrails from incidents is to create a compound note that records the failure, the guardrail decision, and the next steps to evolve the process, ensuring the root cause and reusable rules are tracked for prevention.
blakeoxAnalyze incident logs and reports to identify root causes and quantify tech debt.
daffy0208Generate YAML capability manifests from skill and MCP descriptions.
lgwanaiExtract decisions, lessons, patterns, and surprises into a standardized LEARNINGS.md file.
mmbianco78Automate post-incident retrospectives with 5 Whys and PDCA cycles.
