Skip to content
Weekend-to-Release

End-to-End: Google Antigravity

This playbook is template-first to avoid hallucination. Replace every [RESEARCH REQUIRED] item with verified vendor documentation before production use.

Product Definition Check

Section titled “Product Definition Check”

Before execution, confirm what “Google Antigravity” means in your environment:

  1. Product URL: <RESEARCH REQUIRED>
  2. Official product name: <RESEARCH REQUIRED>
  3. Access model (web app, API, CLI, IDE plugin): <RESEARCH REQUIRED>
  4. Authentication method: <RESEARCH REQUIRED>
  5. Terms and usage limits: <RESEARCH REQUIRED>

If this cannot be confirmed, do not continue with this playbook.

Preflight

Section titled “Preflight”
  1. Confirm repository and target branch.
  2. Confirm toolchain:
  • git --version
  • node --version
  • npm --version
  • auro --version
  1. Confirm Antigravity integration entrypoint:
  • <RESEARCH REQUIRED: launch/connect command>

End-to-End Execution

Section titled “End-to-End Execution”

Step 1: Initialize Governance

Section titled “Step 1: Initialize Governance”
/auro.constitution

Outcome:

  • project principles are explicit before implementation

Step 2: Frame Feature

Section titled “Step 2: Frame Feature”
/auro.charter "<feature request>"

Outcome:

  • user stories, requirements, success criteria, edge cases

Step 3: Design Implementation

Section titled “Step 3: Design Implementation”
/auro.plan

Outcome:

  • architecture, contracts, and phase-gated plan

Step 4: Generate Execution Tasks

Section titled “Step 4: Generate Execution Tasks”
/auro.tasks

Outcome:

  • phased task list with parallel markers

Step 5: Execute

Section titled “Step 5: Execute”
/auro.implement

Outcome:

  • working code tied to charter intent

Validation

Section titled “Validation”

Run verified project commands:

Terminal window
<RESEARCH REQUIRED: lint command>
<RESEARCH REQUIRED: test command>
<RESEARCH REQUIRED: build command>

Validate:

  • success criteria from charter are demonstrably met
  • API or integration contracts pass
  • no unresolved clarification markers remain

Release

Section titled “Release”
  1. Create PR against main.
  2. Include artifacts and validation evidence.
  3. Merge with checks green.
  4. Deploy using verified pipeline:
  • <RESEARCH REQUIRED: deploy workflow name>
  • <RESEARCH REQUIRED: deployment URL>

Risk Controls

Section titled “Risk Controls”
  1. Do not assume unsupported Antigravity capabilities.
  2. Use explicit fallbacks if Antigravity-specific automation is unavailable:
  • run the same ACE flow in a supported agent environment.
  1. Record all deltas between expected and actual behavior.

Research Placeholders To Resolve

Section titled “Research Placeholders To Resolve”
  1. Product identity and official docs
  2. Integration/launch mechanism
  3. Auth and permission model
  4. Rate limits and quotas
  5. CI/CD integration specifics