Implement a feature from its design and connect each covered user journey, a sequence of user actions, to a meaningful test. Run focused checks and assess the full change for effects on existing behavior.
Implement the design with focused tests mapped to each covered CUJ.
Review the instructions the agent will receive before you install.
CLAUDE.md, including framework-owned
instructions, database query names, deprecation notes, and comment style.tests/README.md and tests/_helpers/README.md, then the
nearest existing scenario. Reuse or extend existing coverage before adding
setup. Put input matrices at the lowest reliable layer; add E2E only for a
distinct process, transport, or browser boundary.
otto-impact-assessment and apply it to the full
diff. Record the results in the handoff's impact_assessment and
test_audit.If a requirement turns out to be infeasible, stop building it, mark its CUJs not
covered with the reason, and continue with the rest. Then load feature-demo.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.
Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.