pattern-analysis

Identify and extract reusable patterns from repeated behaviors, workflows, and outcomes. Use when recognizing recurring themes, codifying best practices, extracting workflows from experience, or when pattern, recurring, repeated, or --pattern are mentioned. Micro-skill loaded by codebase-analysis, patternify, and other investigation skills.

⭐4stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025⬇️2downloads

When & Why to Use This Skill

The Pattern Analysis skill is a powerful tool for identifying recurring themes and extracting reusable workflows from complex behaviors and data. By systematically codifying best practices and identifying anti-patterns, it enables the creation of structured SOPs and decision frameworks that drive process consistency and operational excellence.

Use Cases

  • Workflow Extraction: Analyze repeated successful outcomes to define step-by-step standard operating procedures (SOPs) for team-wide adoption.
  • Best Practice Codification: Identify the specific signals and sequences that lead to high-quality results, turning informal experience into formal guidelines.
  • Anti-Pattern Identification: Recognize recurring frustration points or failures to document 'what not to do,' preventing repetitive mistakes and reducing rework.
  • Heuristic Framework Building: Develop condition-action mappings based on observed decision patterns to streamline complex problem-solving and strategic planning.
namepattern-analysis
version1.0.0
descriptionThis 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.

  • 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

Watch for these signal categories:

Category Watch For Indicates
Success Completion, positive feedback, repetition, efficiency Pattern worth codifying
Frustration Backtracking, clarification loops, rework, confusion Anti-pattern to document
Workflow Sequence consistency, decision points, quality gates Process pattern
Orchestration Multi-component coordination, state management, routing Coordination pattern

See signal-types.md for detailed taxonomy.

Four primary pattern types:

Type Characteristics Use When
Workflow Sequential phases, clear transitions, quality gates Process has ordered steps
Orchestration Coordinates components, manages state, routes work Multiple actors involved
Heuristic Condition → action mapping, context-sensitive Repeated decisions
Anti-Pattern Common mistake, causes rework, has better alternative Preventing failures

See pattern-types.md for templates and examples.

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

Strong Pattern Weak Pattern
Consistent structure Varies each use
Transferable to others Requires specific expertise
Handles edge cases Breaks on deviation
Saves time/effort Overhead exceeds value

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

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:

Related skills: