distill repeated observations from experiments and decisions into reusable patterns or anti_patterns for a lean agentic_engineering folder. use when the user wants to promote learnings into playbook guidance, merge overlapping entries, or convert project-specific evidence into reusable markdown docs.
Use this skill to turn project-specific evidence into reusable playbook guidance.
Gather the source evidence. Start from experiments, decisions, or incident notes. Use more than one source when possible.
Decide whether the lesson is a pattern or an anti-pattern.
patterns/ are recommended repeatable approaches.anti_patterns/ are recurring traps, misleading defaults, or harmful shortcuts.Extract the reusable core. Separate the general lesson from project-specific details. Keep enough context to explain when the lesson applies.
Check for duplication. Prefer strengthening or refining an existing file instead of creating overlapping guidance.
Draft clear operational guidance. The final entry should help a future team act differently, not just understand history.
Promote only when at least one of the following is true:
If evidence is weak, call the entry provisional or recommend keeping it in experiments/.
A good pattern explains:
A good anti-pattern explains:
When you find overlapping guidance: