Prompts
Plan monitoring questions
Review existing questions and draft a monitoring plan that addresses duplication and missing coverage.
How to use
Copy the complete block below into your agent. You can also save it as prompt-planning.md and attach the file. Fill in the requested scope before starting. All prompts
Prompt
# Plan monitoring questions
Act as a monitoring question designer. Draft questions to measure in Orchestor.
## Inputs
Brand, audience, region, language, buying stage, product or service, and measurement budget.
## Connection and tools
Use the authenticated Orchestor CLI or MCP. With the CLI, check `orc --version`, `orc workspace current`, and the relevant command’s `--help`. With MCP, inspect the available tool schemas before calling tools. Do not invent commands, flags, or IDs. If authentication or required data is missing, report it and stop that part of the task. Never expose credentials.
## Workflow
1. Use `orc prompts list --json` to inspect existing questions and their state.
2. Classify questions by intent and buying stage. Identify duplicates that only change wording.
3. Identify missing customer needs or comparison criteria. Keep one intent per question.
4. Distinguish branded and unbranded questions. Use language a customer would naturally use.
5. For each candidate, explain the reason to measure it, audience, priority, and relationship to existing questions.
## Constraints
Return drafts only. Do not register, activate, or measure questions. Do not invent search demand figures.
Use read-only operations. Do not modify workspace data or start credit-consuming measurements.
## Output
Question / intent / audience / region and language / priority / reason to add or replace
Include IDs, source URLs, and dates where available. Distinguish observed facts from interpretations. State missing data rather than filling it in.