13 tagged ai agent tools, measured the same way as everything else here.
Browse within: claude-ai 8claude-api 8behaviour-driven-development 5formal-methods 5spec-driven-development 5
Agent Claude Code
Use when requirements, an approved design, or a root cause are clear and one scoped, complete implementation is authorized. Do not use for unresolved exploration, product decisions, diagnosis-only work, or review-only requests.
Agent Claude Code
Use proactively after an implementation or when an existing diff needs correctness, regression, concurrency, compatibility, and meaningful verification review. Do not use for implementation or a dedicated exploitability assessment.
Agent Claude Code
Use proactively when a task needs local repository structure, entry points, ownership, data flow, or change-surface mapping before a decision. Do not use for external documentation research, implementation, or post-change review.
Agent
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
Agent
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new…
Agent
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether…