OpenAgentd workflow for version bumps, release PRs, GitHub releases, and release notes.
Select and create accurate software architecture, workflow, interaction, data, state, and deployment diagrams.
OpenAgentd workflow for keeping the compact feature catalogue and README aligned with user-visible changes.
Research first, propose a step-by-step implementation plan, and wait for explicit approval before writing any code.
Semantic search over the retained OpenAgentd feature catalogue, ADRs, and repository instructions using the turbovec experiment index.
OpenAgentd TDD workflow — write a failing test before the code that makes it pass, reproduce a bug with a test before fixing it. Use when implementing any logic, fixing any bug, or changing any existing behavior in backend (pytest) or frontend (Bun/RTL) code.
OpenAgentd testing reference — environment setup, run commands, and fix patterns for backend (pytest) and frontend (Bun/RTL). Load this for running, fixing, or adding coverage to existing tests. For writing a failing test before new code, use oad/test-driven-development instead.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.