-
Notifications
You must be signed in to change notification settings - Fork 2
Agents
wrm3 edited this page May 30, 2026
·
1 revision
Agents are specialized personas invoked with @agent-name. Each owns a slice of the gald3r workflow (tasks, bugs, planning, review, verification, etc.). Source files live in .gald3r_sys/agents/.
Total agents: 14
| Agent | Description | Source |
|---|---|---|
@g-agnt-code-reviewer |
Use when reviewing code, performing security audits, checking code quality, running @g-code-review, or after any significant implementation. Activate proactively after completing features or when the... | src |
@g-agnt-ideas-goals |
Use when capturing ideas to IDEA_BOARD.md, reviewing the idea board, promoting ideas to tasks, updating goals in PROJECT.md, or when user says "make a note of that", "idea:", "what if we...", "someday... | src |
@g-agnt-infrastructure |
Use when organizing project files, setting up folder structure, managing scope boundaries, preventing over-engineering, updating SUBSYSTEMS.md or subsystem specs, or when files are being placed in wro... | src |
@g-agnt-marketing |
You are gald3r's AI Chief Marketing Officer. You help founders, indie developers, and small teams | src |
@g-agnt-pcac-coordinator |
Cross-project coordination agent. Use when orchestrating parent/child/sibling project relationships - reading topology, triaging INBOX items, broadcasting tasks to children, sending requests to parent... | src |
@g-agnt-platformer |
Use when maintaining cross-platform IDE/agent integration (Cursor, Claude, Copilot, Codex, Antigravity, and 18 others), scanning platform docs for breaking changes, checking platform capability gaps v... | src |
@g-agnt-project |
Use for all project-level concerns - initializing .gald3r/ in a new project, grooming existing .gald3r/ files, filling template placeholders, healing sync issues, creating or updating PLAN.md, writing... | src |
@g-agnt-project-initializer |
Autonomous agent that initializes the full gald3r task management system in a new project, including folder structure, template files, PROJECT.md (v3 consolidated), and initial configuration based on... | src |
@g-agnt-qa-engineer |
Use when reporting bugs, tracking issues, documenting fixes, managing BUGS.md, or running @g-qa/@g-bug-report/@g-bug-fix. Activate proactively when any error, warning, or defect is mentioned - even pr... | src |
@g-agnt-task-manager |
Use when creating, updating, completing, or querying tasks in .gald3r/. Activate for task CRUD operations, status changes, sync checks, task file creation, TASKS.md updates, milestone completion hando... | src |
@g-agnt-test |
Test plan manager for gald3r projects - creates and maintains fast (L1), comprehensive (L2), and regression (L3) test plans. Activates on code review, verification gates, pre-release checks, and @g-te... | src |
@g-agnt-verifier |
Use when verifying completed tasks, reviewing evidence of completion, or cross-checking another agent's implementation. NEVER verify tasks you implemented yourself. Activate when a task shows [] awa... | src |
@g-agnt-workspace-manager |
Use when initializing Workspace-Control, validating workspace manifests, adding/removing workspace members, reviewing member repo boundaries, or running g-wrkspc lifecycle operations. Keeps member rep... | src |
@JOURNAL_FORMAT |
Each gald3r agent has a private, git-tracked journal at | src |
Last updated: 2026-05-30 (gald3r v1.7.0)