Antigravity Installation

Antigravity is Google’s AI-first IDE with native skill support. It uses its own skill and rule system separate from VS Code, making it ideal for Agent Teams Lite.

Prerequisites

Antigravity installed and configured
Git installed for cloning the repository
Access to ~/.gemini/antigravity/ directory (global) or .agent/ (workspace)

Installation Steps

Clone the repository

git clone https://github.com/gentleman-programming/agent-teams-lite.git
cd agent-teams-lite

Choose installation scope

Antigravity supports both global and workspace-specific installations.

Global (Recommended)
Workspace-Specific

Available across all projects:

./scripts/install.sh
# Choose option 6: Antigravity

./scripts/install.sh --agent antigravity

Skills install to ~/.gemini/antigravity/skills/sdd-*/

Only available in current project:

# Copy skills to workspace
mkdir -p .agent/skills
cp -r skills/sdd-* .agent/skills/
cp -r skills/_shared .agent/skills/

Skills install to .agent/skills/sdd-*/

You should see output like:

Installing skills for Antigravity...
  ✓ _shared (3 convention files)
  ✓ sdd-init
  ✓ sdd-explore
  ✓ sdd-propose
  ✓ sdd-spec
  ✓ sdd-design
  ✓ sdd-tasks
  ✓ sdd-apply
  ✓ sdd-verify
  ✓ sdd-archive

  9 skills installed → ~/.gemini/antigravity/skills

Add orchestrator rule

Antigravity uses “rules” for agent instructions. Add the SDD orchestrator as a rule.

Global Rule
Workspace Rule

Add to ~/.gemini/GEMINI.md:

code ~/.gemini/GEMINI.md

Append the contents from examples/antigravity/sdd-orchestrator.md.

Create workspace-specific rule:

mkdir -p .agent/rules
cp examples/antigravity/sdd-orchestrator.md .agent/rules/sdd-orchestrator.md

View orchestrator rule content

The orchestrator rule teaches Antigravity to:

Detect SDD triggers and commands
Read skill files from the appropriate path
Execute skills inline (within current context)
Track state between phases
Follow artifact storage policies (engram/openspec/none)

Key sections:

Operating Mode (delegate-only principle)
Artifact Store Policy
Commands table
Command → Skill Mapping
Engram Artifact Convention

Verify installation

Open Antigravity in any project and open the agent panel.Type:

/sdd-init

Expected response:

Reading sdd-init skill...

✓ Detected stack: [your project's stack]
✓ SDD initialized

Configuration Locations

Global Skills

~/.gemini/antigravity/skills/sdd-*/Available across all projects

Workspace Skills

.agent/skills/sdd-*/Project-specific skills

Rules

~/.gemini/GEMINI.md (global).agent/rules/ (workspace)

Antigravity-Specific Paths

Antigravity does NOT use .vscode/ paths. It has its own convention:

Global: ~/.gemini/antigravity/skills/
Workspace: .agent/skills/ and .agent/rules/

Global vs Workspace

Aspect	Global	Workspace
Skills path	`~/.gemini/antigravity/skills/`	`.agent/skills/`
Rules path	`~/.gemini/GEMINI.md`	`.agent/rules/`
Scope	All projects	Current project only
Team sharing	No	Yes (commit .agent/)
Setup	One-time	Per-project

How It Works

Antigravity has native skill support but runs them inline: Characteristics:

Native skill awareness (Antigravity can discover and suggest skills)
Inline execution (not true sub-agents)
Skills work as structured instructions
Planning phases work well
Implementation guided by skill instructions

Example Usage

Initialize SDD

You: /sdd-init

Antigravity: Reading sdd-init skill from global skills directory...
             
             Analyzing project...
             ✓ Framework: Flutter
             ✓ Language: Dart
             ✓ State management: Riverpod
             ✓ Backend: Firebase
             
             Checking persistence backend...
             ✓ Engram MCP server detected
             
             SDD initialized:
             - Project: my-flutter-app
             - Artifact store: engram
             
             Ready to start building.

Start a New Feature

You: /sdd-new add-offline-mode

Antigravity: Exploring codebase for offline capabilities...
             
             ✓ No offline persistence detected
             ✓ Firebase client: lib/services/firebase_service.dart
             ✓ Hive available (local database)
             
             Creating proposal...
             
             Proposal Summary:
             - Intent: Add offline mode with sync when online
             - Scope: Local storage layer, sync queue, connectivity detection
             - Approach: Hive for local storage, Firebase for sync, connectivity_plus for detection
             - Rollback: Remove Hive boxes, remove sync service, revert to online-only
             
             Artifact stored: sdd/add-offline-mode/proposal
             
             Ready to continue with specs and design?

Fast-Forward Planning

You: /sdd-ff add-offline-mode

Antigravity: Running all planning phases...
             
             Creating specifications...
             ✓ 6 requirements (SHALL statements)
             ✓ 13 scenarios (Given/When/Then)
             ✓ Stored: sdd/add-offline-mode/spec
             
             Creating technical design...
             ✓ Architecture: Repository pattern with local + remote data sources
             ✓ Sync strategy: Queue operations, batch sync on reconnect
             ✓ Conflict resolution: Last-write-wins with timestamp
             ✓ Stored: sdd/add-offline-mode/design
             
             Creating task breakdown...
             ✓ Phase 1: Local storage (3 tasks)
             ✓ Phase 2: Sync service (4 tasks)
             ✓ Phase 3: Connectivity handling (2 tasks)
             ✓ Total: 9 tasks
             ✓ Stored: sdd/add-offline-mode/tasks
             
             All planning complete. Run /sdd-apply to implement.

Artifact Storage

engram (Recommended)
openspec
none

# Auto-detected if Engram MCP server is available
artifact_store:
  mode: engram

Antigravity can use Engram’s MCP server:Naming convention:

title:     sdd/add-offline-mode/proposal
topic_key: sdd/add-offline-mode/proposal
type:      architecture
project:   my-flutter-app

# Only when explicitly requested
artifact_store:
  mode: openspec

Creates file-based artifacts:

openspec/
├── config.yaml
├── specs/
└── changes/
    └── add-offline-mode/
        ├── proposal.md
        ├── specs/
        ├── design.md
        └── tasks.md

# Ephemeral mode - default fallback
artifact_store:
  mode: none

No persistence. Results returned inline.

Team Setup with Workspace Skills

To share SDD with your team using workspace-specific installation:

Install skills to workspace

mkdir -p .agent/skills
cp -r skills/sdd-* .agent/skills/
cp -r skills/_shared .agent/skills/

Add workspace rule

mkdir -p .agent/rules
cp examples/antigravity/sdd-orchestrator.md .agent/rules/sdd-orchestrator.md

Commit to repository

git add .agent/
git commit -m "Add Agent Teams Lite SDD workflow"
git push

Team members get SDD automatically

When team members pull, they get SDD automatically:

git pull
# Open in Antigravity
# /sdd-init is now available

Verification Checklist

Check skills directory (global)

ls ~/.gemini/antigravity/skills/sdd-*/

Should show 9 directories:

sdd-apply/  sdd-design/  sdd-init/  sdd-spec/
sdd-archive/  sdd-explore/  sdd-propose/  sdd-tasks/  sdd-verify/

Check skills directory (workspace)

ls .agent/skills/sdd-*/

Should show same 9 directories if using workspace installation.

Check shared conventions

ls ~/.gemini/antigravity/skills/_shared/
# or
ls .agent/skills/_shared/

Should show:

engram-convention.md
openspec-convention.md
persistence-contract.md

Verify rule is configured

cat ~/.gemini/GEMINI.md | grep -i "sdd"
# or
ls .agent/rules/sdd-orchestrator.md

Test in Antigravity

Open Antigravity agent panel and type:

/sdd-init

Should recognize the command and read the skill.

Troubleshooting

Command not recognized

Problem: Antigravity doesn’t recognize /sdd-initSolutions:

Verify rule is in ~/.gemini/GEMINI.md or .agent/rules/
Check skills are in correct path (NOT .vscode/)
Restart Antigravity to reload configuration
Try alternative phrasing: “Initialize SDD”

Skills not found

Problem: Antigravity can’t read skill filesSolutions:

Check skills path:
- Global: ~/.gemini/antigravity/skills/sdd-*/
- Workspace: .agent/skills/sdd-*/
Do NOT use .vscode/skills/ - that’s for VS Code only
Ensure file permissions allow reading
Verify each skill has SKILL.md file

Wrong path used

Problem: Skills installed to .vscode/ instead of .agent/Solutions:

Remove incorrect installation: rm -rf .vscode/skills/sdd-*

Install to correct location:

mkdir -p .agent/skills
cp -r skills/sdd-* .agent/skills/

Update rule to reference .agent/skills/ path

Rule not loading

Problem: Orchestrator behavior not activeSolutions:

Check global rule: ~/.gemini/GEMINI.md
Check workspace rule: .agent/rules/sdd-orchestrator.md
Ensure file is readable
Restart Antigravity after making changes

Next Steps

Quick Start

Learn the SDD workflow

Commands Reference

Complete command documentation

Engram Setup

Install recommended persistence

Team Workflows

Share SDD with your team

Get Started

Installation

Guides

Commands

Prerequisites

Installation Steps

Configuration Locations

Global Skills

Workspace Skills

Rules

Antigravity-Specific Paths

Global vs Workspace

How It Works

Example Usage

Initialize SDD

Start a New Feature

Fast-Forward Planning

Artifact Storage

Team Setup with Workspace Skills

Verification Checklist

Troubleshooting

Next Steps

Quick Start

Commands Reference

Engram Setup

Team Workflows

​Prerequisites

​Installation Steps

​Configuration Locations

Global Skills

Workspace Skills

Rules

​Antigravity-Specific Paths

​Global vs Workspace

​How It Works

​Example Usage

​Initialize SDD

​Start a New Feature

​Fast-Forward Planning

​Artifact Storage

​Team Setup with Workspace Skills

​Verification Checklist

​Troubleshooting

​Next Steps

Quick Start

Commands Reference

Engram Setup

Team Workflows

Prerequisites

Installation Steps

Configuration Locations

Antigravity-Specific Paths

Global vs Workspace

How It Works

Example Usage

Initialize SDD

Start a New Feature

Fast-Forward Planning

Artifact Storage

Team Setup with Workspace Skills

Verification Checklist

Troubleshooting

Next Steps