fworks-tech/agenthood - Page 2

validation-and-enforcement

Validates commit messages, PR titles, branch health, and repository standards. Use to enforce conventions and run health checks before merge.

the-reviewer

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.

the-operator

Manages runtime health, deployment, incidents, rollback, and monitoring for agenthood services.

the-strategist

Translates ambiguous goals into structured problem statements, success criteria, and ranked priorities before the Architect starts planning. Use when requirements are vague, a feature request needs refinement, or the path from "what" to "how" is unclear. The…

the-architect

Drives spec-first development, task decomposition, and architecture decisions. Use before any non-trivial implementation begins. Use when requirements are unclear, a design decision needs to be recorded, or a feature needs to be broken into implementable…

the-auditor

Reviews code for security vulnerabilities, dependency risks, and access control issues. Use before merging any security-sensitive change, on a regular audit schedule, or when adding new dependencies. The Auditor assumes breach and reads code the way an…

the-debugger

Diagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior. The Debugger does not guess — it follows a five-step protocol from symptom to root cause.

the-scribe

Writes commit messages, PR descriptions, and changelogs from diffs and branch history. Use whenever staging a commit, opening a PR, or preparing a release. The Scribe turns your diff into prose worth reading.

the-tester

Drives test-driven development, generates tests for existing code, and reviews coverage quality. Use before implementing any behavior (write the test first), when generating tests for untested code, or when assessing whether tests actually verify the right…

the-warden

Detects code smell, complexity violations, architectural boundary breaches, dead code, and dependency decay in project code. Runs on every PR diff and on demand for full codebase scans. The chaos does not arrive all at once — The Warden is here for the…