antigravity-init 1.0.0 → 1.0.2

package/.agent/skills/agile-management/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: agile-management
+description: Manage projects using Agile methodology driven by "Context Engineering". Ensures dynamic feature changes are handled systematically, establishing clear context for every task to avoid hallucination.
+---
+
+# Agile Management & Context Engineering
+
+## Overview
+
+This skill brings the **BMAD (Breakthrough Method for Agile Ai Driven Development)** philosophy to your project. It focuses on **Context Engineering**—the art of preparing "crystal-clear" context for AI agents so they can implement tasks without needing to search for information or make assumptions.
+
+**Core Principles:**
+1.  **Context Before Code**: Never start coding without a fully defined User Story that includes all technical context (Models, APIs, UX).
+2.  **Agile Adaptability**: Features change. We use "Stories" as the unit of work. If requirements change, we write a new story or update the draft.
+3.  **Single Source of Truth**: Data models, APIs, and patterns are pulled from Architecture/PRD docs, not invented on the fly.
+
+## Usage
+
+### 1. Planning (Context Engineering)
+Before implementing any feature, you must create a **User Story** that engineers the context for the developer.
+
+```bash
+# Run the context engineering task
+@agile-management/tasks/create-story
+```
+
+### 2. Implementation
+Once a story is status `Draft` or `Approved`, it is handed to a Developer Agent (or you acting as one). The Developer Agent simply follows the "Dev Notes" and "Tasks" in the story.
+
+### 3. Architecture First
+This skill relies on having documentation to pull context from.
+-   `docs/architecture/tech-stack.md`
+-   `docs/architecture/unified-project-structure.md`
+-   `docs/data-models.md`, etc.
+
+*If these do not exist, the first task is to create them.*
+
+## The Workflow
+
+1.  **Brainstorm**: Use `brainstorming` skill to define the features for the next Epic/Sprint.
+2.  **Engineer Context**: Use `create-story` task to prepare the granular `story.md`.
+3.  **Implement**: Execute the story tasks.
+4.  **Review**: Verify against Acceptance Criteria.
+
+## Roles
+
+-   **Scrum Master (Context Engineer)**: You (the agent) when running `create-story`. Your job is to be rigorous, citing sources, and ensuring the "Developer" has everything they need.
+-   **Developer**: You (the agent) when implementing. You are "dumb" in the sense that you follow the story and architecture exactly without inventing new patterns.

package/.agent/skills/agile-management/tasks/create-story.md

@@ -0,0 +1,48 @@
+<!-- Based on BMAD™ Core create-next-story task -->
+
+# Create User Story (Context Engineering)
+
+## Purpose
+To prepare a comprehensive, self-contained, and actionable story file. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent.
+
+## Prerequisite Check
+1.  **Docs Existence**: Check if `docs/architecture` exists. If not, STOP and suggest creating `tech-stack.md` and `project-structure.md` first.
+2.  **Epic/Features**: Have a clear idea of what feature (Epic) this story belongs to.
+
+## Steps
+
+### 1. Gather Requirements
+-   Analyze the user's request or the PRD/Epic file to extract the **User Story Statement** (As a... I want... So that...) and **Acceptance Criteria (AC)**.
+-   *Strict Rule*: If AC is vague, ask the user to clarify. "Fast" is not an AC; "Loads in < 200ms" is.
+
+### 2. Gather Architecture Context (The Engineering Part)
+You must read the project's architecture documentation to find *existing* patterns to reuse.
+-   **Data Models**: Read `docs/data-models.md` or schema files. Which models are involved?
+-   **APIs**: Read `docs/api-spec.md` or route files. Which endpoints are needed?
+-   **UI/UX**: Read `docs/design-system.md` or components. Which components to use?
+
+**CRITICAL**: You must Cite your sources. Example: `[Source: docs/data-models.md#User]`
+
+### 3. Populate Story
+Create a new file `docs/stories/[epic-number].[story-number].[short-title].md` using the template below.
+
+**Template Location**: `.agent/skills/agile-management/templates/story.md`
+
+### 4. Dev Notes Section (The "Dumb Agent" Enabler)
+In the `Dev Notes` section of the story, you must write:
+-   **Exact file paths** to create/modify.
+-   **Exact variable names** or database columns (from gathered context).
+-   **Pseudo-code** or logic flow if complex.
+-   **Testing Strategy**: How to verify this specific story.
+
+*Goal*: The Developer Agent should generally **not** need to look at other files. All context is here.
+
+### 5. Final Review
+-   [ ] Does the story have a `Status: Draft`?
+-   [ ] Are all Acceptance Criteria testable?
+-   [ ] Are there `Dev Notes` with specific technical details?
+-   [ ] Did you avoid inventing new architecture patterns (hallucination)?
+
+## Output
+-   The created `.md` file path.
+-   A summary of the technical context found.

package/.agent/skills/agile-management/templates/story.md

@@ -0,0 +1,44 @@
+# Story {{epic_num}}.{{story_num}}: {{story_title}}
+
+**Status**: Draft
+**Role**: Scrum Master / Context Engineer
+
+## 1. User Story
+**As a** {{role}}
+**I want** {{action}}
+**So that** {{benefit}}
+
+## 2. Acceptance Criteria
+1. [ ] {{criteria_1}}
+2. [ ] {{criteria_2}}
+3. [ ] ...
+
+## 3. Technical Context (Dev Notes)
+*Context Engineered from Architecture & PRD. Developer: Do not deviate without approval.*
+
+### Data Models
+- {{model_name}}: {{details}} [Source: {{source_file}}]
+
+### API Endpoints
+- {{method}} {{path}}: {{description}} [Source: {{source_file}}]
+
+### UI/Components
+- {{component_name}}: {{usage_instructions}} [Source: {{source_file}}]
+
+### File Locations
+- New: `src/features/...`
+- Modify: `src/components/...`
+
+## 4. Implementation Tasks
+- [ ] **Task 1**: {{task_description}}
+    - [ ] Subtask: {{subtask_details}}
+- [ ] **Task 2**: {{task_description}}
+    - [ ] Subtask: {{subtask_details}}
+- [ ] **Task 3**: Write Unit/Integration Tests
+
+## 5. Testing Strategy
+- **Unit Tests**: {{unit_test_plan}}
+- **Manual Verification**: {{manual_verification_steps}}
+
+## 6. Questions / Risks
+- {{question_or_risk}}

package/README.md

@@ -0,0 +1,46 @@
+# 🚀 Antigravity Init
+
+**The ultimate agentic coding toolkit scaffolder.**
+
+Instantly supercharge any project with the **Antigravity** agentic framework. This tool installs the latest autonomous coding agents, skills, rules, and workflows directly into your project.
+
+## ✨ Features
+
+*   **⚡ Instant Setup**: One command to scaffold the entire Antigravity `.agent` configuration.
+*   **🤖 AI Agents**: Deploys specialized agents (Architect, Planner, Code Reviewer, Security Auditor, etc.).
+*   **🧠 Skills Library**: Installs a rich library of skills (Brainstorming, TDD, Git Workflows, etc.).
+*   **🛡️ Rules & Workflows**: Enforces coding standards and provides ready-to-use agentic workflows.
+*   **🔄 Smart Updates**: Use the same command to update your existing configuration to the latest version.
+
+## 📦 Usage
+
+You don't need to install anything globally. Just run the initialization command in your project root:
+
+### Standard Usage (Recommended)
+```bash
+npx antigravity-init
+```
+
+### Using the Short Alias
+If you prefer the shorter command `ag-init`, you must specify the package name:
+```bash
+npx -p antigravity-init ag-init
+```
+
+## 🛠️ What it does
+
+Running the command will:
+1.  **Download** the latest `antigravity-init` package.
+2.  **Copy/Update** the following directories in your current folder:
+    *   `/.agent` - Contains all agent definitions, skills, and workflows.
+    *   `/.shared` - Shared utilities and configurations.
+3.  **Overwrite** existing configuration files to ensure you have the latest standards (Force Update).
+
+## ⚠️ Notes
+
+*   **Force Update**: This tool is designed to keep your agentic config in sync with the source of truth. Running it on an existing project **will overwrite** files in `.agent` and `.shared`.
+*   **Project Structure**: Your project code remains untouched. Only the Antigravity agent configuration directories are modified.
+
+## 📄 License
+
+ISC

package/bin/cli.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 const fs = require('fs-extra');
 const path = require('path');

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "antigravity-init",
-    "version": "1.0.0",
+    "version": "1.0.2",
     "description": "The Antigravity project scaffolder and updater.",
     "main": "bin/cli.js",
     "bin": {
@@ -27,4 +27,4 @@
         "fs-extra": "^11.2.0",
         "picocolors": "^1.0.0"
     }
-}
+}