---

name: pattern-analysis version: 1.0.0 description: This skill should be used when recognizing recurring themes, codifying best practices, extracting reusable workflows, or when "pattern", "recurring", or "repeated" are mentioned.

Pattern Analysis

Identify signals → classify patterns → validate with evidence → document for reuse.

<when_to_use>

• Recognizing recurring themes in work or data
• Codifying best practices from experience
• Extracting workflows from repeated success
• Identifying anti-patterns from repeated failures
• Building decision frameworks from observations

NOT for: single occurrences, unvalidated hunches, premature abstraction

</when_to_use>

<signal_identification>

Watch for these signal categories:

See signal-types.md for detailed taxonomy.

</signal_identification>

<pattern_classification>

Four primary pattern types:

See pattern-types.md for templates and examples.

</pattern_classification>

<evidence_thresholds>

Codification Criteria

Don't codify after first occurrence. Require:

• 3+ instances — minimum repetition to establish pattern
• Multiple contexts — works across different scenarios
• Clear boundaries — know when to apply vs not apply
• Measurable benefit — improves outcome compared to ad-hoc approach

Quality Indicators

</evidence_thresholds>

<progressive_formalization>

Observation (1-2 instances):

• Note for future reference
• "This worked well, watch for recurrence"

Hypothesis (3+ instances):

• Draft informal guideline
• Test consciously in next case

Codification (validated pattern):

• Create formal documentation
• Include examples and constraints

Refinement (ongoing):

• Update based on usage
• Add edge cases

</progressive_formalization>

Loop: Observe → Classify → Validate → Document

1. Collect signals — note successes, failures, recurring behaviors
2. Classify pattern type — workflow, orchestration, heuristic, anti-pattern
3. Check evidence threshold — 3+ instances? Multiple contexts?
4. Extract quality criteria — what makes it work?
5. Document pattern — name, when, what, why
6. Test deliberately — apply consciously, track variance
7. Refine — adjust based on feedback

ALWAYS:

• Require 3+ instances before codifying
• Validate across multiple contexts
• Document both when to use AND when not to
• Include concrete examples
• Track pattern effectiveness over time

NEVER:

• Codify after single occurrence
• Abstract without evidence
• Ignore context-sensitivity
• Skip validation step
• Assume transferability without testing

Deep-dive documentation:

• signal-types.md — detailed signal taxonomy
• pattern-types.md — pattern templates and examples

Related skills:

• patternify — pattern discovery from conversations
• codebase-analysis — uses pattern analysis for code investigation
• report-findings — presenting discovered patterns