generate-agentlisted

# Generate agent Turn a described role into a real agent persona — a stable team member with a clear mandate, named operating standards, and guardrails, that reads like it shipped with the framework's own roster. ## When to use Whenever the user asks (from the Customize page, or directly in chat) to **add an agent** — "I want a data-migration specialist", "add an accessibility reviewer", "create an agent for API contract reviews" — or when `propose-customizations` proposed an agent candidate the user picked. ## Method ### 1. Clarify before generating A one-line ask ("add a data agent") is under-specified. Use `.spectoflow/skills/clarify`'s reflex — one targeted question at a time, each with a recommended default — until you know: - **What this role owns that no existing agent already owns.** Read `.spectoflow/agents/*.md` first — a new agent for a capability an existing one already covers is redundant; either the existing agent should gain a skill instead (see `generate-skill`), or this really is a distinct capability. - **Which capability it serves.** Pick the closest match from `.spectoflow/capabilities.md`'s palette, or note that this genuinely needs a new capability name (rare — most real needs fit the existing palette; propose adding to the palette only when nothing fits). - **What skill(s) it runs.** An agent without at least one skill in `uses` has no procedure to execute — either an existing skill fits, or this request also needs `generate-skill` (sequ