Browse Skills

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31

maestro.md

188

1 export maestro

2 from "xenitV1/claude-code-maestro"

3 Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

2026-01-31