By jaxvy
PM → Architect → Coder → Tester pipeline for Android, working in Claude Code and Antigravity.
PM → Architect → Coder → Tester for a vague Android idea, with human gates
Produce an implementation plan from a feature spec or description (Architect only, no build)
Refine a vague Android idea into an approved feature spec (PM only, no build)
Architect → Coder → Tester with automated reviewer gates (architect-reviewer + code-reviewer) that bounce work back on feedback
Architect → Coder → Tester for an already-specified Android feature
Use this agent to review an implementation plan produced by adt-android-architect before any code is written. Trigger after the Architect finishes in the /build-auto-reviewed flow, or when the user says "review the plan". Requires pipeline_artifacts/{slug}/implementation-plan.md to exist. Outputs an APPROVED / CHANGES REQUESTED verdict — it never edits the plan.
Use this agent to produce a concrete implementation plan for an Android feature. Trigger after adt-android-pm (in /build-guided flow) or directly (in /build-auto flow). Requires either pipeline_artifacts/feature.md to exist (/build-guided) or a clear feature description in the prompt (/build-auto).
Use this agent to review the Coder's uncommitted changes against the implementation plan and the project's conventions. Trigger after adt-android-coder finishes in the /build-auto-reviewed flow, or when the user says "review the code/diff". Requires uncommitted changes in the working tree and pipeline_artifacts/{slug}/implementation-plan.md. Outputs an APPROVED / CHANGES REQUESTED verdict — it never edits code.
Use this agent to implement Android code from an implementation plan. Trigger after the adt-android-architect agent finishes, or when the user says "implement", "build it", or "code section X". Requires pipeline_artifacts/{slug}/implementation-plan.md to exist.
Use this agent to refine a vague Android feature idea into a concrete feature description. Trigger only when the user runs /build-guided, or when they say "help me think through", "what should X look like", or "I have an idea for". DO NOT use for /build-auto — /build-auto assumes the feature is already specified.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A reusable PM → Architect → Coder → Tester pipeline for Android projects,
working identically in Claude Code and
Antigravity. Distributed as per-file symlinks
into each consuming project — no whole-dir symlinks, no forced migration
of your existing .claude/ or .agents/ content.
Once installed in a project, open it in Claude Code or Antigravity and run a
slash command from the chat prompt. The build-* commands run the full
pipeline end to end (the suffix tells you whether a human is in the loop, and
whether automated reviewers gate each phase); the two plan-* commands run just
one early phase and stop, so you can research or design without committing to a
build.
/build-guided <vague idea>Human-in-the-loop variant. PM → Architect → Coder → Tester with approval gates between phases. Use when the idea is rough and you want the PM to refine it before any code is written.
/build-guided add a recently-played carousel to the home screen
The PM agent turns that into a concrete feature spec at
pipeline_artifacts/<slug>/feature.md and pauses for your sign-off. After
you approve, the Architect produces an implementation plan, the Coder
implements it, and the Tester verifies — each phase stops for review.
/build-auto <specified feature>Fully automatic variant. Architect → Coder → Tester, no gates. Use when the feature is already specified.
/build-auto add a "Save draft on background" hook to ComposeViewModel that persists the current input to Room every 2s and restores it on launch
The Architect writes the plan, the Coder implements it, the Tester runs
verification on a device via the auto-mobile MCP server. Artifacts for
every run land under pipeline_artifacts/<slug>/.
/build-auto-reviewed <specified feature>Same shape as /build-auto (no PM phase, no human gates), but each producing
phase is followed by an automated reviewer that can send the work back. Use when
you want a higher-quality unattended run and are willing to spend more tokens for
it.
/build-auto-reviewed add a "Save draft on background" hook to ComposeViewModel that persists the current input to Room every 2s and restores it on launch
The Architect writes the plan, then @adt-android-architect-reviewer reviews
it; the Coder implements, then @adt-android-code-reviewer reviews the diff. On
each gate, if the reviewer requests changes, the producing agent is re-run with
the feedback — at most twice per gate. If a reviewer still isn't satisfied
after the second re-run, the pipeline stops and reports rather than shipping
work the reviewer rejected. A clean run then hands off to the Tester as usual.
When you want a plan but not a build, run just one phase — each runs a single phase, stops after writing its artifact, and works identically in Claude Code and Antigravity. Their output chains into a build command (or each other) later.
/plan-research <vague idea>Runs only the PM. Turns a rough idea into a concrete, unambiguous feature spec
at pipeline_artifacts/<slug>/feature.md, asking clarifying questions along
the way — then stops.
/plan-research add a recently-played carousel to the home screen
Feed the resulting feature.md to /plan-design, /build-auto, or
/build-guided when you're ready.
/plan-design <feature.md path | specified feature>Runs only the Architect. Produces an implementation plan at
pipeline_artifacts/<slug>/implementation-plan.md from either a feature.md
(e.g. from /plan-research) or a clear feature description — then stops.
/plan-design pipeline_artifacts/recently-played-carousel/feature.md
Feed the resulting plan to /build-auto or /build-guided to implement and
verify it.
Two paths:
adt-* agents and the /build-auto, /build-auto-reviewed, /build-guided, /plan-research, and /plan-design slash commands without per-project setup. Does not wire up Antigravity (no .agents/workflows/ files, no agents.md persona stubs, no .gitignore block)..gitignore block, and inlines persona stubs into .agents/agents.md for Antigravity. This is the only supported path for Antigravity — Antigravity has no plugin marketplace.The two are not mutually exclusive — you can install the plugin in Claude Code and still run install.sh in Antigravity projects.
From inside the Claude Code CLI:
/plugin marketplace add jaxvy/agentic-dev-team
/plugin install agentic-dev-team@adt-pipeline
npx claudepluginhub jaxvy/agentic-dev-team --plugin agentic-dev-teamComprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use