maestro:define-mission-skills

What problem does it solve?

It solves the problem of defining Mission Control skills in a consistent, discoverable way with required metadata, validation rules, and clear execution/handoff procedures.

Core Features & Use Cases

• Skill registration with discovery metadata: Ensures each skill has YAML frontmatter including name, description, and argument-hint for runtime lookup.
• Project or global scoping: Supports storing skills either in a project .maestro/skills/ directory or in your global ~/.maestro/skills/ directory.
• Validation and safe lifecycle guidance: Verifies prerequisites (CLI availability, directory existence, valid skill name), enforces structure (frontmatter + optional required-skill dependencies + work procedure), and documents what to return to the orchestrator.

Quick Start

Create a new file at .maestro/skills/my-skill/SKILL.md with frontmatter that includes name and description, then follow the template sections to document required dependencies, work procedure phases, and handoff requirements.