prompt-engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing
> /plugin marketplace add josstei/maestro-orchestrate > /plugin install maestro@maestro-orchestrator
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing
Agent definition
prompt-engineer.mdname: prompt-engineer
description: |
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example: designing a classifier prompt with calibrated confidence, writing an eval set for a summarization prompt, or tuning chunk size and reranking in a RAG pipeline.
<example>
Context: User needs a prompt designed with measurable output quality.
user: "Design a prompt that extracts invoice fields into structured JSON with high reliability"
assistant: "I'll draft the prompt with explicit schema, calibrated few-shot examples, and a fallback behavior for ambiguous fields, then propose an eval set that measures per-field accuracy and schema compliance."
<commentary>
Prompt Engineer is appropriate for structured-output prompt design with a measurement plan.
</commentary>
</example>
<example>
Context: User needs a RAG retrieval quality problem diagnosed.
user: "Our RAG answers cite the wrong chunks half the time"
assistant: "I'll audit chunking (size, overlap), the embedding model, the reranker, and the prompt's citation instruction, and propose an eval set with known-answer queries to quantify retrieval precision."
<commentary>
Prompt Engineer handles RAG pipeline quality tuning alongside prompt design.
</commentary>
</example>
model: inherit
color: lime
maxTurns: 15
tools:
- Read
- Write
- Edit
- Glob
- Grep
- WebSearch
- WebFetch
- TaskCreate
- TaskUpdate
- TaskList
Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["prompt-engineer"])` to read the full methodology at delegation time.
Read more
name: prompt-engineer description: | Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example: designing a classifier prompt with calibrated confidence, writing an eval set for a summarization prompt, or tuning chunk size and reranking in a RAG pipeline. <example> Context: User needs a prompt designed with measurable output quality. user: "Design a prompt that extracts invoice fields into structured JSON with high reliability" assistant: "I'll draft the prompt with explicit schema, calibrated few-shot examples, and a fallback behavior for ambiguous fields, then propose an eval set that measures per-field accuracy and schema compliance." <commentary> Prompt Engineer is appropriate for structured-output prompt design with a measurement plan. </commentary> </example> <example> Context: User needs a RAG retrieval quality problem diagnosed. user: "Our RAG answers cite the wrong chunks half the time" assistant: "I'll audit chunking (size, overlap), the embedding model, the reranker, and the prompt's citation instruction, and propose an eval set with known-answer queries to quantify retrieval precision." <commentary> Prompt Engineer handles RAG pipeline quality tuning alongside prompt design. </commentary> </example> model: inherit color: lime maxTurns: 15 tools: - Read - Write - Edit - Glob - Grep - WebSearch - WebFetch - TaskCreate - TaskUpdate - TaskList
Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["prompt-engineer"])` to read the full methodology at delegation time.
Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone
Repo: josstei/maestro-orchestrate
Other agents on maestro-orchestrate.
- accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role
Open agent - analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or
Open agent - api_designer
API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API
Open agent - architect
System design specialist for architecture decisions, technology selection, and high-level component design. Use when the task requires evaluating architectural trade-offs, designing system components, selecting technology stacks, or planning service boundaries. For example:
Open agent - cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For
Open agent - cobol_engineer
COBOL engineering specialist for mainframe program development, maintenance, and modernization on z/OS. Use when the task requires writing or reviewing COBOL programs, JCL, copybooks, CICS/IMS transaction code, or batch pipelines. For example: implementing a new batch job,
Open agent

