maestro:setup

Create essential configuration files for Maestro project onboarding.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro:setup
Source: https://github.com/ReinaMacCredy/Maestro-CLI/tree/main/.codex/skills/maestro%3Asetup
Command: npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the initial setup of a new project within the Maestro framework, ensuring all necessary context files are created and configured correctly.

Core Features & Use Cases

  • Project Scaffolding: Creates essential context files like product.md, tech-stack.md, and workflow.md.
  • Contextualization: Detects project maturity (brownfield/greenfield) and infers settings from the codebase.
  • Use Case: When starting a new project, run this Skill to establish the foundational project context, which guides all subsequent Maestro operations.

Quick Start

Run the maestro setup skill to initialize your project context.

Frequently Asked Questions about maestro:setup

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

FAQPage Schema
How do I initialize project context for an existing codebase?

Scaffolding project context creates essential configuration files like product.md, tech-stack.md, and workflow.md automatically. This establishes the foundational project definition required to guide all subsequent operations within the orchestrator framework.

What is the best way to scaffold configuration files for a new project?

Scaffolding project context creates essential configuration files like product.md, tech-stack.md, and workflow.md automatically. This establishes the foundational project definition required to guide all subsequent operations within the orchestrator framework.

Can I use automated project onboarding for both greenfield and brownfield codebases?

Automated project onboarding supports both greenfield and brownfield codebases. It handles project initialization by detecting project maturity and inferring the appropriate settings to create consistent configuration files across all operations.

Do I need manual configuration files to run orchestrator workflows?

Project context initialization creates essential configuration files like product.md, tech-stack.md, and workflow.md to establish foundational project definition. This ensures consistent settings across all orchestrator operations for both new and existing codebases.

Why does project context need to be defined before running orchestrator tasks?

Project context needs definition first because it establishes the foundational settings that guide all subsequent orchestrator operations. Scaffolding ensures consistent project definition across all skills by generating essential configuration files upfront.

Are there limitations when inferring codebase settings during project initialization?

Inferring codebase settings during project initialization relies on analyzing existing code and conducting user interviews. For greenfield projects lacking existing code, the Skill depends more heavily on user interviews to accurately scaffold the initial context files.