Spawn Templates

GPTClaudeDeepSeek··▲ 651 copies·updated 2026-07-14

spawn-templates.prompt

# Spawn-Prompt Templates

Ready-to-adapt prompts the orchestrator pastes into the Task tool when
spawning each specialist. Sub-agents have **no conversation history** — the
spawn prompt is everything they know, so every template carries the six
required elements from [chapter 03 §2](../playbook/03-communication-protocol.md):
branch, task, file lists, specs/contracts verbatim, prior-stage status, and
the rules.

Every template ends with the same **safety rails** line. Do not trim it —
it is stated here *and* enforced in
[templates/settings.json.template](../templates/settings.json.template);
prose alone has failed before ([chapter 08, note 3](../playbook/08-field-notes.md)).

> Rails (repeated verbatim in each template):
> *Never run git or gh. Never reset any database except `{{TEST_DB_NAME}}`.
> Never write secrets into files or reports. Report in the canonical format
> from the communication protocol.*

---

## backend-dev + frontend-dev (Stage 2 — spawn as a parallel pair, one message)

fill the variables

This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{{TEST_DB_NAME}

Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo alikwan/claude-code-agent-team (MIT). A "Spawn Templates" 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.