← ClaudeAtlas

maestro-prompt-designerlisted

Turn an idea or requirements conversation into an approved, persistent task specification for Maestro. Use before routing when scope, current phase, constraints or acceptance criteria need clarification; works with grilling in the same conversation. Does not select skills or implement the task.
rodovalhofs/maestro · ★ 2 · AI & Automation · score 63
Install: claude install-skill rodovalhofs/maestro
# Maestro Prompt Designer Prepare the complete user's objective for Maestro. Use the user's language. Capture decisions rather than optimizing a prompt for keyword matching. ## Work with the conversation Read relevant earlier decisions before asking anything. When `grilling` is active, it owns the interview: ask one selection-changing question at a time, recommend an answer and wait. Consolidate each answer instead of starting a second interview. If grilling is unavailable, conduct that same focused interview yourself. Resolve facts from targeted project inspection; leave product decisions to the user. Do not read credentials or unrelated projects to establish context. Distinguish confirmed decisions, verified facts (with file references), preferences, assumptions, rejected alternatives and unresolved questions. Never silently turn an assumption into approval. Reuse answers and authorizations already given. Revisit them only when a new fact makes them materially inconsistent or insufficient. ## Build the specification Identify the requested outcome, present state, current development phase, required capabilities, dependencies, constraints, deliverables and observable acceptance criteria. Describe capabilities, not skill names, unless the user explicitly picks a skill. Do not impose a technology or remove a user's choice without discussion. For a full project, retain the entire outcome. Break work into phases with clear inputs, deliverables, validation and completion st