tq-forge-agentlisted

# /tq-forge-agent — force-agent scaffold ## When to use You want a multi-turn, persona-driven agent with a rigid output format — not a one-shot procedural skill. The agent lives as a 5-file directory under `$TQ_FORGE_HOME/sandbox/forged-agents/<slug>/`: `AGENT.md`, `system-prompt.md`, `tools.json`, `trigger-conditions.md`, `example-tasks.md`. `/tq-forge-promote` is the only path that moves it into production. ## Procedure ```bash export TQ_FORGE_HOME="${TQ_FORGE_HOME:-$HOME/.tq-forge}" S="${CLAUDE_PLUGIN_ROOT:-${TQ_FORGE_HOME:-$HOME/.tq-forge}/install}/scripts"; T="${CLAUDE_PLUGIN_ROOT:-${TQ_FORGE_HOME:-$HOME/.tq-forge}/install}/templates/agent-templates" source "$S/common.sh" && tq_ensure_home ``` 1. **Check the halt flag.** If `$TQ_FORGE_HOME/halt.flag` exists, queue and exit: ```bash test -f "$TQ_FORGE_HOME/halt.flag" && bash "$S/forge-checkpoint.sh" queue "<intent>" && exit 0 ``` 2. **Pick the agent kind** via AskUserQuestion (default to the closest match by the intent's verbs — search -> researcher, build -> coder, monitor -> ops-manager): `researcher`, `coder`, `business-analyst`, `ops-manager`, `scraper`, `reviewer`, `sales-agent`, `custom`. 3. **Pick a slug.** Lowercase, hyphenated, <=32 chars. Confirm if ambiguous. 4. **Check for collisions.** ```bash for d in "$SANDBOX_AGENTS/<slug>" "$CLAUDE_SKILLS_DIR/agents/<slug>"; do test -e "$d" && echo "EXISTS: $d" done ``` 5. **Read the template + your context.** ```bash cat