maestro-design

Author validated Maestro product-specs via an ADR-aligned grill interview protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns your product intent into a validated, committed maestro product-spec by running an interview-driven “grill protocol” that resolves ambiguity against glossary and architectural constraints.

Core Features & Use Cases

  • Interview-driven spec authoring: Guides one decision-tree branch at a time (acceptance criteria, non-goals, risk class, mode, work type, dependencies) with one question per turn.
  • Glossary + ADR consistency checks: Challenges new or conflicting terminology against CONTEXT.md and references committed ADR rules when verifiable.
  • Committed spec output for downstream execution: Writes a validated .maestro/specs/<slug>.md ready for maestro task from-spec or maestro mission new.
  • Human-safe, approval-friendly workflow: Focuses on producing the spec artifact only (not planning or implementation).

Quick Start

Use this skill to produce a ready-to-run product spec by having maestro-design grill your requirements until it writes a validated .maestro/specs/<slug>.md.

Frequently Asked Questions about maestro-design

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

FAQPage Schema
How do I validate product spec requirements before implementation?

Validating product spec requirements involves running an interview-driven grill protocol that resolves ambiguity against glossary and architectural constraints, producing a committed `.maestro/specs/<slug>.md` file. This ensures acceptance criteria align with ADR rules before execution.

What is the grill interview protocol for spec authoring?

The grill interview protocol for spec authoring is a one-question-per-turn decision-tree process that resolves acceptance criteria, non-goals, risk class, mode, work type, and dependencies. It challenges conflicting terminology against CONTEXT.md to ensure glossary consistency.

How do I check glossary consistency and ADR alignment in product specs?

Checking glossary consistency and ADR alignment requires cross-referencing new terminology against CONTEXT.md and committed architectural decision records. The grill protocol identifies conflicts during the interview and enforces verifiable code cross-referencing where possible.

Can I use this interview protocol to refine an existing product proposal?

Yes, you can use this interview protocol to refine existing product proposals before planning or implementation. The grill process applies to both authoring new spec work and refining existing proposals for maestro mission and task execution.

Does the spec validation process handle downstream task planning?

No, the spec validation process focuses exclusively on producing the validated spec artifact. It outputs a committed `.maestro/specs/<slug>.md` ready for downstream execution like `maestro task from-spec` or `maestro mission new`, but does not perform planning or implementation.

What's the best way to write committed maestro product specs from user requirements?

Writing committed maestro product specs requires an ADR-aligned grill interview that resolves requirements one decision-tree branch at a time. Final validation outputs a `.maestro/specs/<slug>.md` file, ensuring the spec is approval-friendly and ready for downstream execution.