evolution-from-patches

name	evolution-from-patches
description	Distill recurring prevention points from project patch history into learned project rules.
compatibility	opencode

When to use

• The project has accumulated patches and should turn them into reusable guidance.

Procedure

1. Read recent patch artifacts.
2. Group related prevention points.
3. Remove generic noise.
4. Produce a compact learned-rules document.
5. Save an evolution note with what changed.

Rules

• Learned rules must be project-specific.
• Prefer traceable, repeated patterns over one-off anecdotes.