/analyze
| Keywords | Capability | Prefix | |----------|------------|--------| | analyze, scan, audit, map, identify | analyzer | ANALYZE | | design, plan, strategy, refactoring-plan | designer | DESIGN | | refactor, implement, fix, apply | refactorer | REFACTOR | | validate, build,
$ npx -y skills add catlog22/maestro-flow --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/analyze
Context preview
What this command does when you run it.
| Keywords | Capability | Prefix | |----------|------------|--------| | analyze, scan, audit, map, identify | analyzer | ANALYZE | | design, plan, strategy, refactoring-plan | designer | DESIGN | | refactor, implement, fix, apply | refactorer | REFACTOR | | validate, build,
Command definition
analyze.mdAnalyze Task
Signal Detection
| Keywords | Capability | Prefix | |----------|------------|--------| | analyze, scan, audit, map, identify | analyzer | ANALYZE | | design, plan, strategy, refactoring-plan | designer | DESIGN | | refactor, implement, fix, apply | refactorer | REFACTOR | | validate, build, test, verify, compile | validator | VALIDATE | | review, audit-code, quality, check-code | reviewer | REVIEW |
Dependency Graph
Natural ordering tiers:
- Tier 0: analyzer (knowledge gathering -- no dependencies)
- Tier 1: designer (requires analyzer output)
- Tier 2: refactorer (requires designer output)
- Tier 3: validator, reviewer (validation requires refactored artifacts, can run in parallel)
Complexity Scoring
| Factor | Points | |--------|--------| | Per capability | +1 | | Cross-domain refactoring | +2 | | Parallel branches requested | +1 per branch | | Serial depth > 3 | +1 | | Multiple targets (independent mode) | +2 |
Results: 1-3 Low, 4-6 Medium, 7+ High
Role Minimization
- Cap at 5 roles
- Merge overlapping capabilities
- Absorb trivial single-step roles
Output
Write {run_dir}/work/team/task-analysis.json:
{
"task_description": "<original>",
"pipeline_type": "<single|fan-out|independent|auto>",
"capabilities": [{ "name": "<cap>", "prefix": "<PREFIX>", "keywords": ["..."] }],
"dependency_graph": { "<TASK-ID>": { "role": "<role>", "blockedBy": ["..."], "priority": "P0|P1|P2" } },
"roles": [{ "name": "<role>", "prefix": "<PREFIX>", "inner_loop": false }],
"complexity": { "score": 0, "level": "Low|Medium|High" },
"parallel_mode": "<auto|single|fan-out|independent>",
"max_branches": 5
}Read more
Analyze Task
Signal Detection
| Keywords | Capability | Prefix | |----------|------------|--------| | analyze, scan, audit, map, identify | analyzer | ANALYZE | | design, plan, strategy, refactoring-plan | designer | DESIGN | | refactor, implement, fix, apply | refactorer | REFACTOR | | validate, build, test, verify, compile | validator | VALIDATE | | review, audit-code, quality, check-code | reviewer | REVIEW |
Dependency Graph
Natural ordering tiers:
- Tier 0: analyzer (knowledge gathering -- no dependencies)
- Tier 1: designer (requires analyzer output)
- Tier 2: refactorer (requires designer output)
- Tier 3: validator, reviewer (validation requires refactored artifacts, can run in parallel)
Complexity Scoring
| Factor | Points | |--------|--------| | Per capability | +1 | | Cross-domain refactoring | +2 | | Parallel branches requested | +1 per branch | | Serial depth > 3 | +1 | | Multiple targets (independent mode) | +2 |
Results: 1-3 Low, 4-6 Medium, 7+ High
Role Minimization
- Cap at 5 roles
- Merge overlapping capabilities
- Absorb trivial single-step roles
Output
Write {run_dir}/work/team/task-analysis.json:
{
"task_description": "<original>",
"pipeline_type": "<single|fan-out|independent|auto>",
"capabilities": [{ "name": "<cap>", "prefix": "<PREFIX>", "keywords": ["..."] }],
"dependency_graph": { "<TASK-ID>": { "role": "<role>", "blockedBy": ["..."], "priority": "P0|P1|P2" } },
"roles": [{ "name": "<role>", "prefix": "<PREFIX>", "inner_loop": false }],
"complexity": { "score": 0, "level": "Low|Medium|High" },
"parallel_mode": "<auto|single|fan-out|independent>",
"max_branches": 5
}Intent-driven workflow orchestration for multi-agent AI development — adaptive lifecycle engine, self-reinforcing knowledge graph, and visual dashboard for Claude Code, Gemini, Codex & more
Repo: catlog22/maestro-flow
Other commands on maestro-flow.
- /maestro-companion
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.
Open command - /maestro-fork
Create or sync session worktree for parallel dev
Open command - /maestro-guard
Manage editing boundary restrictions
Open command - /maestro-impeccable
Use when designing, auditing, polishing, improving, or codifying frontend UI — websites, dashboards, landing pages, components, design systems
Open command - /maestro-init
Initialize project with auto state detection
Open command - /maestro-issue
Intent-driven issue lifecycle management — describe what you want in natural language (报告一个 bug / 列出开放 issue / 关掉 ISS-xxx / 关联到 task / 扫描发现问题) and the workflow routes to the right operation. Operates on .workflow/issues/. 知识管理走 /maestro-knowledge;knowhow 沉淀走
Open command

