
Extract Pattern
Turns working solutions into reusable templates so you're not reinventing the wheel every time you solve something twice. It walks you through identifying what actually worked in a workflow, generalizing it into a pattern with clear "when to use" and "when NOT to use" sections, then testing if it actually applies elsewhere. The format is sensible: problem, template, variants, pitfalls, examples. Honestly most useful after you've iterated on something enough times that you're tired of explaining it, or when you catch yourself copy-pasting the same approach across projects. Pairs with calibrate to keep your pattern library consistent.
- skills.sh installs
- 340
- GitHub stars
- 602
- last updated
- Aug 21, 2026
Install
$ npx -y skills add sharpdeveye/maestro --skill extract-pattern --agent claude-codeInstalls into .claude/skills of the current project.
Files
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:
Sponsors
Details
- Repository
- github.com/sharpdeveye/maestro
- Category
- DevOps & CI/CD
- First seen
- Jun 3, 2026