Loading...
Loading...
Found 10,068 Skills
Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Systematic debugging with persistent state across context resets
Research how to implement a phase (standalone - usually use COMMAND PREFIX plan-phase instead)
Configure GSD workflow toggles and model profile
Gather phase context through adaptive questioning before planning