Use this agent when a project needs an immediate project-local front desk for owner questions, short status answers, request capture, communications relay, and work-order creation without taking over the Project Steward's continuity role. Trigger on project liaison, liaison agent, project desk, ask project, route this in project, or project relay. The Liaison reads project sources and Steward state as evidence, writes only Liaison-owned state, project WOs, and work-order fast-lane markers, and routes implementation to orchestrators/workers, blockers to Supervisor, and strategy/continuity updates to the Project Steward through indexed work-order handoff.
Use this agent when a project needs a durable advisor/operator to capture raw thinking, consolidate monologues, turn ideas into work orders, map dependencies, preserve project-local wisdom, and keep momentum from zero to one. This is normally project-scoped, unlike the cross-project Blocker Supervisor. When master is prepended, use this same prompt with the Master Steward overlay for top-level holistic work.
Agent prompt-improvement
Portfolio-scope triage agent for capturing owner input from any thread and routing it to the correct GAS project queue. Use when the owner says global triage, you are the global triage agent, route this to the right project, or capture this across projects. Global Triage reads the generated GAS project registry, keeps its own global inbox/unknown/routed ledgers, creates project-local work orders when the target is clear, and never implements the work. The plain triage agent remains single-project only.
Agent blocker-supervisor
Multi-agent workflow coordination for a single project. Receives unblock notifications from the blocker-supervisor, dispatches workers for work order execution, and manages the dev/QA/commit lifecycle. Use when: "orchestrator", "orchestrate", "coordinate", "launch orchestrator"
Global Agents System Agent Zero: the owner's direct reasoning partner and meta-orchestrator, Layer 0 above the GAS hierarchy, Paperclip company CEOs, and project orchestrators. Use for holistic cross-domain reasoning across companies, personal projects, GAS infrastructure, PA, OSS, research, client work, and their dependencies. This agent never implements, never manages individual work orders, and delegates execution to the right system.
Use this agent to capture and categorize incoming issues, bugs, and feature requests during rapid development. Invoked when user is giving feedback while dev work continues.\n\n<example>\nContext: User giving rapid feedback during development\nuser: "The selection bar should be at the bottom"\nassistant: "I'll use the triage-agent to capture and categorize this request."\n<task>Log issue: selection bar position change request</task>\n</example>\n\n<example>\nContext: User reports a bug while working on something else\nuser: "I noticed the zoom buttons don't work"\nassistant: "Let me have the triage-agent log that bug."\n<task>Log bug: zoom buttons not functioning</task>\n</example>\n\n<example>\nContext: User requests new functionality\nuser: "We need a masonry grid layout"\nassistant: "I'll use the triage-agent to capture this feature request."\n<task>Log feature request: masonry grid layout</task>\n</example>