maestro-dev

Guide maestroCLI feature development through hexagonal architecture workflows.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-dev-leonardo-corte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-dev
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.claude/skills/maestro-dev
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-dev-leonardo-corte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

maestro-dev turns adding new maestroCLI capabilities from an unclear, error-prone effort into a reliable workflow with consistent architecture, wiring, and testing conventions.

Core Features & Use Cases

  • Hexagonal architecture guidance: Keeps changes aligned across CLI commands, MCP server tools, use-cases, ports, and adapters using a fixed execution order.
  • Port-first development: Defines or extends TypeScript port interfaces to describe required inputs/outputs while staying framework-agnostic.
  • Adapter + use-case implementation: Implements adapters against concrete backends and moves business logic into pure use-cases for testability.
  • Command and MCP tool wiring: Adds thin CLI/MCP surfaces that delegate to shared use-case logic and return consistent results.
  • Error handling and state safety: Standardizes actionable MaestroError hints and explicit state transition validation to prevent invalid operations.
  • Test and verification workflow: Establishes unit and integration test placement and mandates build/test verification before proceeding.

Quick Start

Use maestro-dev when implementing a new maestro feature, and follow the sequence: define the needed port, implement the adapter, wire a use-case, add the CLI command and MCP tool, then create focused tests and run build and tests.

Frequently Asked Questions about maestro-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new command to a CLI using hexagonal architecture?▼

Adding a new command to a CLI using hexagonal architecture requires defining a port interface first, implementing a backend adapter, wiring a pure use-case, and adding a thin command layer before running tests.

What is port-first development for TypeScript CLI features?▼

Port-first development for TypeScript CLI features means defining framework-agnostic interfaces for required inputs and outputs before implementing concrete adapters and moving business logic into pure, testable use-cases.

How do I extend an MCP server with new tools without duplicating logic?▼

To extend an MCP server without duplicating logic, add a thin MCP tool surface that delegates to the same shared pure use-case logic used by your CLI commands, ensuring consistent results.

What is the best way to handle errors and invalid state transitions in CLI development?▼

Handling errors and invalid state transitions in CLI development effectively requires standardizing actionable error hints and applying explicit state transition validation to prevent invalid operations.

Do I need bun to build and test ports and adapters architecture?▼

Yes, you need bun to execute the build and test verification cycle required to validate ports, adapters, use-cases, and command wiring before proceeding with further development.

Why should business logic be moved into pure use-cases when building CLI tools?▼

Moving business logic into pure use-cases when building CLI tools separates core behavior from I/O operations, making your code highly testable and keeping command and tool layers thin.