2026-03-13 06:02:36Claude (Dev):
[mcp] Add manager prompt template with documentation step to Agent Workflow
design/agent workflow.md ..
@@ 60,6 60,53 @@
Other managers running in parallel are not blocked.
+
## Manager Prompt Template
+
+
When launching a manager, the orchestrator's prompt should include all of the following:
+
+
```
+
You are a phase manager for the wikibot.io project. Follow the /proceed
+
workflow: plan with Groucho, implement, review with Chico and Zeppo,
+
fix critical/important issues, report back.
+
+
## Task: {task_id} — {task_title}
+
+
**Target:** {repo} at {path}
+
**Branch:** Create `{branch_name}` from `main`
+
+
**Context — existing infrastructure:**
+
{bullet list of relevant infra: deployed resources, file paths, URLs,
+
Pulumi config, related repos}
+
+
**Description:**
+
{from task spec}
+
+
**Deliverables:**
+
{from task spec}
+
+
**Acceptance criteria:**
+
{from task spec}
+
+
**Important notes:**
+
{task-specific guidance, gotchas, references to other code}
+
- Do NOT use `git add -A` — stage specific files only
+
- When done, do NOT push. Report back with results.
+
+
**Documentation:** When you are done, write your results to the dev wiki
+
using the `mcp__dev-wiki-container__write_note` tool. Create or update
+
the page `Dev/{task_id} Summary` with:
+
- Status and acceptance criteria results
+
- Architecture decisions with rationale
+
- Files changed
+
- Concerns or open questions
+
- Test results
+
```
+
+
Key elements the orchestrator must not forget:
+
- **Infrastructure context** — resource IDs, URLs, file paths the manager will need
+
- **Coordination notes** — what other managers are running in parallel, which files to avoid
+
- **Documentation step** — managers write their own results to the dev wiki
+
## Invoking the Workflow
The orchestrator uses the `/proceed` skill to load the workflow instructions, then follows the delegation model above. The key rule: **the orchestrator coordinates, managers implement.**