Agent Claude Code
Read repo-root AGENTS.md first, then docs/backend-architecture.md, then LEARNINGS.md, before planning or implementing.
Vibe-coded tower-defense game built by an AI agent pipeline (planner → coder → smoke-tester → reviewer) running across Claude Code, Cursor, and VS Code Copilot.
Agent Claude Code
Read repo-root AGENTS.md first, then docs/backend-architecture.md, then LEARNINGS.md, before planning or implementing.
Agent Claude Code
Implements features and fixes from a HANDOFF:PLAN. Writes and edits code, runs focused local checks, keeps scope minimal. Tests-first for any domain code under internal/ /. Hands off to smoke-tester via HANDOFF:IMPLEMENTATION.
Agent Claude Code
Creates GitHub issues, labels, and milestones using gh CLI. Breaks down features into runnable, well-labelled issues with binary acceptance criteria and local verification steps. Standalone — does not delegate to planner or any other agent unless explicitly asked.
Agent Claude Code
Picks the next GitHub issue from the current milestone, creates the linked task branch, explores the codebase, and writes a detailed technical plan. Analysis and planning only — no source edits, no commits. Delegates to the coder via HANDOFF:PLAN.
Agent Claude Code
Walks every assumption in HANDOFF:PLAN and tries to refute it by reading the repo. Upholds the plan (handing off to coder) or refutes it (escalating to user). Read-only — no code edits, no commits.
Agent Claude Code
Final review of the diff for correctness, security, conventions, and spec conformance. Waits for CI green. On clean verdict, appends one line to LEARNINGS.md and signals merge-ready. On blocking findings, emits HANDOFF:FIX to coder. Read-only on source code.
Agent Claude Code
Runs smoke tests after implementation — build, unit tests, start server if applicable, curl live endpoints, report results. Observer/recorder only — does not modify anything. Hands off to reviewer on pass, back to coder on fail.
Agent
Implement a plan from IssuePlanner, run Bastion formatters and linters, commit, and open a PR.
Agent
Fetch GitHub issues, research the Bastion codebase, clarify with you, and produce a detailed implementation plan before handing off to IssueCoder. Use at the start of milestone work or when you need a plan before coding.
Agent
Walks every assumption in HANDOFF:PLAN and tries to refute it by reading the repo. Upholds the plan (handing off to Coder) or refutes it (escalating to user). Read-only — no code edits, no commits.
Agent
Read-only reviewer. Reads the PR diff, identifies issues, and hands off to IssueCoder to fix them. Never writes code.
Agent
Run smoke tests after implementation — build, unit tests, start server if applicable, curl live endpoints, report results.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: