Zensu connects Antigravity to your product's feature record. Specs guide implementation, native agents review the change, and evidence stays attached to the work — from the first plan to release readiness.
> /zensu-implement ZEN-42 feature record spec · acceptance criteria · security implementation code · tests · linked documentation native review findings → fixes → self-review completion gate current evidence required before done
Your team and your agent work from the same feature. The implementation leaves a record your next review can actually inspect.
Your spec, acceptance criteria, user journeys and security classification live together in Zensu. Ask Antigravity to implement a feature and it works against that shared record, then links the source, tests and documentation back to it.
Native Antigravity reviewers inspect the change from different perspectives. Findings feed the review and fix cycle; the final self-review closes the chain. A reviewer finishing does not, by itself, make the feature complete.
An armed workflow checks test results, source changes and review completion before it can finish. Missing or stale evidence keeps the gate closed. Zensu's release-readiness checks keep security, documentation and journeys in view.
Implement directly within the workflow, then verify the result and complete the review chain. The plugin does not require a failing test before the first code change in this mode.
Enable strict RED → GREEN with /zensu-tdd-mode. The phase gate requires the failing-test evidence before production edits. Review and completion checks remain part of the workflow.
An explicit choice to work outside the workflow is respected. Secret scanning and configured tool guards have their own settings; strict test-first enforcement is opt-in.
Zensu runs directly in Antigravity. Claude Code is not required. The typed Zensu CLI connects your agent to the product record.
32 skills cover planning, implementation, security, documentation, review, session recovery and delivery. Seven native role profiles support the review and worker flows. Try /zensu-help for orientation.
Live checks exercise command loading, native rules, reviewer identity, blocked writes and stop-and-resume behavior. IDE importing and execution remain unverified; this guide describes the CLI installation.
Get the v0.2.0 native ZIP and its checksum from our integration team: Request the Antigravity package.
Use a logged-in Antigravity CLI, Node.js, Bash, Git and the authenticated Zensu CLI. Run zensu auth login if needed. Windows requires Git Bash; live acceptance here was performed on macOS.
Verify the ZIP against the supplied SHA-256 checksum before extracting it. Use the native package; a source archive needs its own installer.
Extract outside Antigravity's installed plugin directory, then run:
unzip zensu-antigravity-native-v0.2.0.zip -d zensu-agy agy plugin install ./zensu-agy/zensu agy plugin validate ~/.gemini/config/plugins/zensu agy plugin list
Open a fresh CLI conversation and run /zensu-help. To update, verify and extract the new package first, run agy plugin uninstall zensu, then install the new directory. This removes obsolete plugin files while preserving Zensu configuration.
Google operates a curated Antigravity Marketplace. Zensu is being prepared for inclusion and is not yet listed. Until Google approves a listing, use the native package through our integration team.
For package access, setup and Marketplace questions, contact [email protected]. Zensu is provided by MK IT Consulting.
Request Zensu access