/extract-pattern
Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
$ npx -y skills add sharpdeveye/maestro --skill extract-pattern --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/extract-pattern
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
SKILL.md
extract-pattern.SKILL.mdname: extract-pattern
description: "Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows."
argument-hint: "[source workflow or area]"
category: utility
version: 2.0.0
user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
---
Turn working solutions into reusable patterns. Every successful workflow contains patterns that are applicable beyond their original context.
Step 1: Identify What Worked
Review the workflow and identify components that:
- Solved a common problem in a particularly effective way
- Would be useful in other workflows or projects
- Required significant iteration to get right
- Represent a non-obvious solution
Step 2: Generalize the Pattern
Transform the specific solution into a reusable template:
**From specific** → **To general pattern**:
## Pattern: [Name]
**Problem**: What recurring problem does this solve?
**When to use**: When is this pattern appropriate?
**When NOT to use**: When is this pattern inappropriate?
**Template**: Copy-pastable starting point with customization markers.
**Variants**: Common variations for different contexts.
**Pitfalls**: What went wrong during development and how it was fixed.
**Examples**: 1-2 concrete examples.
Step 3: Test Reusability
- Apply the template to a different but analogous problem
- Confirm the customization points are sufficient
- Verify the documentation is clear enough for someone unfamiliar with the original
| Workflow Element | Extract As | |-----------------|-----------| | Effective prompt structure | Prompt template with customization points | | Tool chain that works well | Pipeline pattern with data flow diagram | | Error handling strategy | Resilience pattern with implementation guide | | Evaluation approach | Quality assurance pattern with scoring rubric | | Context management technique | Context pattern with budget guidance | | Agent coordination protocol | Orchestration pattern with handoff templates |
Recommended Next Step
After extracting patterns, run `/calibrate` to ensure the new patterns are consistent with existing project conventions.
**NEVER**:
- Extract patterns from workflows that don't work reliably
- Over-generalize (if it only applies to one case, document it as a solution, not a pattern)
- Skip the "when NOT to use" section
- Extract without testing reusability
Read more
name: extract-pattern description: "Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows." argument-hint: "[source workflow or area]" category: utility version: 2.0.0 user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
---
Turn working solutions into reusable patterns. Every successful workflow contains patterns that are applicable beyond their original context.
Step 1: Identify What Worked
Review the workflow and identify components that:
- Solved a common problem in a particularly effective way
- Would be useful in other workflows or projects
- Required significant iteration to get right
- Represent a non-obvious solution
Step 2: Generalize the Pattern
Transform the specific solution into a reusable template:
**From specific** → **To general pattern**:
## Pattern: [Name] **Problem**: What recurring problem does this solve? **When to use**: When is this pattern appropriate? **When NOT to use**: When is this pattern inappropriate? **Template**: Copy-pastable starting point with customization markers. **Variants**: Common variations for different contexts. **Pitfalls**: What went wrong during development and how it was fixed. **Examples**: 1-2 concrete examples.
Step 3: Test Reusability
- Apply the template to a different but analogous problem
- Confirm the customization points are sufficient
- Verify the documentation is clear enough for someone unfamiliar with the original
| Workflow Element | Extract As | |-----------------|-----------| | Effective prompt structure | Prompt template with customization points | | Tool chain that works well | Pipeline pattern with data flow diagram | | Error handling strategy | Resilience pattern with implementation guide | | Evaluation approach | Quality assurance pattern with scoring rubric | | Context management technique | Context pattern with budget guidance | | Agent coordination protocol | Orchestration pattern with handoff templates |
Recommended Next Step
After extracting patterns, run `/calibrate` to ensure the new patterns are consistent with existing project conventions.
**NEVER**:
- Extract patterns from workflows that don't work reliably
- Over-generalize (if it only applies to one case, document it as a solution, not a pattern)
- Skip the "when NOT to use" section
- Extract without testing reusability
Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and 6 more.
Repo: sharpdeveye/maestro
Other skills on maestro.
- /accelerate
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Open skill - /adapt-workflow
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
Open skill - /agent-workflow
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
Open skill - /amplify
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Open skill - /calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Open skill - /capture
Capture a session summary — what was done, what decisions were made, and what to do next.
Open skill

