agent-factorylisted

# Forge agent factory When the loop meets a recurring task type no roster agent fits, mint a new agent — deliberately, gated, and logged. The roster must never regrow into a graveyard (spec §6.4). ## First decision: agent or skill? - A reusable *procedure or body of knowledge* → it's a **skill**: defer to `skill-creator`. Do not build an agent for it. - A *role that gets spawned with its own context, model, and output contract* → it's an **agent**: continue here. ## Scope: project-local vs. global - **Project-local (default):** write `.forge/agents/<name>.md`, git-tracked with the repo (format: `docs/conventions.md` → ".forge/agents/"). Then mirror the file to `.claude/agents/<name>.md` so the running harness discovers it; the `.forge/` copy is canonical. - **Global (only when useful across projects):** write to the plugin's `agents/`. - **Archive (kernel fast-path minting only):** write `.forge/agents/archive/<name>.md` — never mirrored, never standing-team membership on creation (`docs/conventions.md`, "Ephemeral agent tier — 2026-07-19 (fg-b0301, spec-b71f3a)"). `/forge:agent`'s human-initiated flow never targets this tier; the fast-path mint flow that writes here is fg-b0302's own build. ## Build the agent (anatomy — spec §6.1) Start from `references/agent-template.md` and fill every section: mission (single purpose), attached skills, default routing (model + effort + one-line justification), optional tool allowlist, output contract (exact struc