Specialist Prompts
# Specialist Prompt Templates These prompt templates are used by the `run` subcommand (Step 5) when dispatching specialist agents. Each template is self-contained — agents share no context with each other or with the parent session. All templates use these placeholders: - `{ID}`: The investigation identifier - `{QUESTION}`: The investigation question from BRIEF.md - `{REPO_PATH}`: The absolute path to the repository (repo specialists only) - `$INVESTIGATIONS_DIR`: The resolved investigations directory path --- ## Data Access Rules (all specialists) **Never use Bash to query databases or external APIs.** Use MCP tools: - MongoDB: `mcp__mongodb__find`, `mcp__mongodb__aggregate` - Datadog logs: `mcp__datadog__get_logs` - Snowflake: `mcp__snowflake__run_sql` - ClickUp: `mcp__clickup__get_task`, `mcp__clickup__search_tasks` Direct CLI tools (`mongosh`, `curl datadoghq.com`) are blocked and will fail. --- ## code-archaeologist
fill the variables
This prompt has 3 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{ID}{QUESTION}{REPO_PATH}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo john-wilmes/claude-agentic-coding-playbook (MIT). A "Specialist Prompts" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
businesscommunitygeneral
source
john-wilmes/claude-agentic-coding-playbook · MIT