pattern-analysis

Pattern analysis identifies signals from repeated behaviors, groups them into reusable workflows, and documents them with trigger conditions, core steps, and rationale. Patterns require 3+ validated instances across contexts with documented usage guidelines and traceable success or failure evidence.

Patterns capture successful, repeatable workflows to codify best practices; anti-patterns document common mistakes and inefficiencies to avoid. Both require cross-context validation and documented evidence to distinguish repeatable signals from isolated incidents.

Yes. Pattern analysis extracts reusable workflows from documented successes by identifying recurring behaviors, classifying them as sequential or orchestration workflows, and creating guidelines with examples and evidence gates for consistent reuse.

A pattern requires at least 3 documented instances, cross-context validation to confirm it generalizes, usage guidelines with concrete examples, and traceable evidence through success, failure, and quality gates.

Pattern classification categorizes workflows into sequential (step-by-step execution), orchestration (coordinated multi-component execution), and heuristic (rule-based decision) types. Classification enables consistent documentation and reuse across different contexts.