gsd-antigravity-kit 1.32.0 → 2.0.0

package/.agent/skills/gsd/references/commands/{gsd-list-phase-assumptions.md → phase/list-phase-assumptions.md}

@@ -1,15 +1,16 @@
 ---
-name: gsd-list-phase-assumptions
-description: "Surface Antigravity's assumptions about a phase approach before planning"
+name: gsd:list-phase-assumptions
+description: Surface Antigravity's assumptions about a phase approach before planning
 argument-hint: "[phase]"
 allowed-tools:
   - Read
   - Bash
   - Grep
   - Glob
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
 
-
 <objective>
 Analyze a phase and present Antigravity's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
 

package/.agent/skills/gsd/references/commands/{gsd-plan-phase.md → phase/plan-phase.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-plan-phase
-description: "Create detailed phase plan (PLAN.md) with verification loop"
+name: gsd:plan-phase
+description: Create detailed phase plan (PLAN.md) with verification loop
 argument-hint: "[phase] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--prd <file>] [--reviews] [--text]"
 agent: gsd-planner
 allowed-tools:
@@ -13,8 +13,9 @@ allowed-tools:
   - AskUserQuestion
   - WebFetch
   - mcp__context7__*
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
 

package/.agent/skills/gsd/references/commands/{gsd-remove-phase.md → phase/remove-phase.md}

@@ -1,14 +1,15 @@
 ---
-name: gsd-remove-phase
-description: "Remove a future phase from roadmap and renumber subsequent phases"
-argument-hint: "<phase-number>"
+name: gsd:remove-phase
+description: Remove a future phase from roadmap and renumber subsequent phases
+argument-hint: <phase-number>
 allowed-tools:
   - Read
   - Write
   - Bash
   - Glob
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
 

package/.agent/skills/gsd/references/commands/{gsd-research-phase.md → phase/research-phase.md}

@@ -1,14 +1,15 @@
 ---
-name: gsd-research-phase
-description: "Research how to implement a phase (standalone - usually use /gsd-plan-phase instead)"
+name: gsd:research-phase
+description: Research how to implement a phase (standalone - usually use /gsd-plan-phase instead)
 argument-hint: "[phase]"
 allowed-tools:
   - Read
   - Bash
   - Task
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
 
-
 <objective>
 Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.
 
@@ -40,7 +41,7 @@ Normalize phase input in step 1 before any directory lookups.
 ## 0. Initialize Context
 
 ```bash
-INIT=$(node ".agent/skills/gsd/bin/gsd-tools.cjs" init phase-op "$ARGUMENTS")
+.agent/skills/gsd/bin/gsd-tools.cjs" init phase-op "$ARGUMENTS")
 if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
 ```
 
@@ -48,13 +49,13 @@ Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`
 
 Resolve researcher model:
 ```bash
-RESEARCHER_MODEL=$(node ".agent/skills/gsd/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)
+.agent/skills/gsd/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)
 ```
 
 ## 1. Validate Phase
 
 ```bash
-PHASE_INFO=$(node ".agent/skills/gsd/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")
+.agent/skills/gsd/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")
 ```
 
 **If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.

package/.agent/skills/gsd/references/commands/{gsd-secure-phase.md → phase/secure-phase.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-secure-phase
-description: "Retroactively verify threat mitigations for a completed phase"
+name: gsd:secure-phase
+description: Retroactively verify threat mitigations for a completed phase
 argument-hint: "[phase number]"
 allowed-tools:
   - Read
@@ -11,8 +11,9 @@ allowed-tools:
   - Grep
   - Task
   - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Verify threat mitigations for a completed phase. Three states:
 - (A) SECURITY.md exists — audit and verify mitigations

package/.agent/skills/gsd/references/commands/{gsd-ui-phase.md → phase/ui-phase.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-ui-phase
-description: "Generate UI design contract (UI-SPEC.md) for frontend phases"
+name: gsd:ui-phase
+description: Generate UI design contract (UI-SPEC.md) for frontend phases
 argument-hint: "[phase]"
 allowed-tools:
   - Read
@@ -12,8 +12,9 @@ allowed-tools:
   - WebFetch
   - AskUserQuestion
   - mcp__context7__*
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Create a UI design contract (UI-SPEC.md) for a frontend phase.
 Orchestrates gsd-ui-researcher and gsd-ui-checker.

package/.agent/skills/gsd/references/commands/{gsd-ui-review.md → phase/ui-review.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-ui-review
-description: "Retroactive 6-pillar visual audit of implemented frontend code"
+name: gsd:ui-review
+description: Retroactive 6-pillar visual audit of implemented frontend code
 argument-hint: "[phase]"
 allowed-tools:
   - Read
@@ -10,8 +10,9 @@ allowed-tools:
   - Grep
   - Task
   - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Conduct a retroactive 6-pillar visual audit. Produces UI-REVIEW.md with
 graded assessment (1-4 per pillar). Works on any project.

package/.agent/skills/gsd/references/commands/{gsd-validate-phase.md → phase/validate-phase.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-validate-phase
-description: "Retroactively audit and fill Nyquist validation gaps for a completed phase"
+name: gsd:validate-phase
+description: Retroactively audit and fill Nyquist validation gaps for a completed phase
 argument-hint: "[phase number]"
 allowed-tools:
   - Read
@@ -11,8 +11,9 @@ allowed-tools:
   - Grep
   - Task
   - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Audit Nyquist validation coverage for a completed phase. Three states:
 - (A) VALIDATION.md exists — audit and fill gaps

package/.agent/skills/gsd/references/commands/{gsd-workstreams.md → phase/workstreams.md}

@@ -1,70 +1,71 @@
----
-name: gsd-workstreams
-description: "Manage parallel workstreams — list, create, switch, status, progress, complete, and resume"
-allowed-tools:
-  - Read
-  - Bash
----
-
-
-# /gsd-workstreams
-
-Manage parallel workstreams for concurrent milestone work.
-
-## Usage
-
-`/gsd-workstreams [subcommand] [args]`
-
-### Subcommands
-
-| Command | Description |
-|---------|-------------|
-| `list` | List all workstreams with status |
-| `create <name>` | Create a new workstream |
-| `status <name>` | Detailed status for one workstream |
-| `switch <name>` | Set active workstream |
-| `progress` | Progress summary across all workstreams |
-| `complete <name>` | Archive a completed workstream |
-| `resume <name>` | Resume work in a workstream |
-
-## Step 1: Parse Subcommand
-
-Parse the user's input to determine which workstream operation to perform.
-If no subcommand given, default to `list`.
-
-## Step 2: Execute Operation
-
-### list
-Run: `node "$GSD_TOOLS" workstream list --raw --cwd "$CWD"`
-Display the workstreams in a table format showing name, status, current phase, and progress.
-
-### create
-Run: `node "$GSD_TOOLS" workstream create <name> --raw --cwd "$CWD"`
-After creation, display the new workstream path and suggest next steps:
-- `/gsd-new-milestone --ws <name>` to set up the milestone
-
-### status
-Run: `node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"`
-Display detailed phase breakdown and state information.
-
-### switch
-Run: `node "$GSD_TOOLS" workstream set <name> --raw --cwd "$CWD"`
-Also set `GSD_WORKSTREAM` for the current session when the runtime supports it.
-If the runtime exposes a session identifier, GSD also stores the active workstream
-session-locally so concurrent sessions do not overwrite each other.
-
-### progress
-Run: `node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"`
-Display a progress overview across all workstreams.
-
-### complete
-Run: `node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
-Archive the workstream to milestones/.
-
-### resume
-Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
-
-## Step 3: Display Results
-
-Format the JSON output from gsd-tools into a human-readable display.
-Include the `${GSD_WS}` flag in any routing suggestions.
+---
+name: gsd:workstreams
+description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
+allowed-tools:
+  - Read
+  - Bash
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
+---
+
+# /gsd-workstreams
+
+Manage parallel workstreams for concurrent milestone work.
+
+## Usage
+
+`/gsd-workstreams [subcommand] [args]`
+
+### Subcommands
+
+| Command | Description |
+|---------|-------------|
+| `list` | List all workstreams with status |
+| `create <name>` | Create a new workstream |
+| `status <name>` | Detailed status for one workstream |
+| `switch <name>` | Set active workstream |
+| `progress` | Progress summary across all workstreams |
+| `complete <name>` | Archive a completed workstream |
+| `resume <name>` | Resume work in a workstream |
+
+## Step 1: Parse Subcommand
+
+Parse the user's input to determine which workstream operation to perform.
+If no subcommand given, default to `list`.
+
+## Step 2: Execute Operation
+
+### list
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream list --raw --cwd "$CWD"`
+Display the workstreams in a table format showing name, status, current phase, and progress.
+
+### create
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream create <name> --raw --cwd "$CWD"`
+After creation, display the new workstream path and suggest next steps:
+- `/gsd-new-milestone --ws <name>` to set up the milestone
+
+### status
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream status <name> --raw --cwd "$CWD"`
+Display detailed phase breakdown and state information.
+
+### switch
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream set <name> --raw --cwd "$CWD"`
+Also set `GSD_WORKSTREAM` for the current session when the runtime supports it.
+If the runtime exposes a session identifier, GSD also stores the active workstream
+session-locally so concurrent sessions do not overwrite each other.
+
+### progress
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream progress --raw --cwd "$CWD"`
+Display a progress overview across all workstreams.
+
+### complete
+.agent/skills/gsd/bin/gsd-tools.cjs" workstream complete <name> --raw --cwd "$CWD"`
+Archive the workstream to milestones/.
+
+### resume
+Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
+
+## Step 3: Display Results
+
+Format the JSON output from gsd-tools into a human-readable display.
+Include the `${GSD_WS}` flag in any routing suggestions.

package/.agent/skills/gsd/references/commands/{gsd-analyze-dependencies.md → project/analyze-dependencies.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-analyze-dependencies
-description: "Analyze phase dependencies and suggest Depends on entries for ROADMAP.md"
+name: gsd:analyze-dependencies
+description: Analyze phase dependencies and suggest Depends on entries for ROADMAP.md
 allowed-tools:
   - Read
   - Write
@@ -8,8 +8,9 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Analyze the phase dependency graph for the current milestone. For each phase pair, determine if there is a dependency relationship based on:
 - File overlap (phases that modify the same files must be ordered)
@@ -26,7 +27,7 @@ Then suggest `Depends on` updates to ROADMAP.md.
 <context>
 No arguments required. Requires an active milestone with ROADMAP.md.
 
-Run this command BEFORE `/gsd:manager` to fill in missing `Depends on` fields and prevent merge conflicts from unordered parallel execution.
+Run this command BEFORE `/gsd-manager` to fill in missing `Depends on` fields and prevent merge conflicts from unordered parallel execution.
 </context>
 
 <process>

package/.agent/skills/gsd/references/commands/project/explore.md

@@ -0,0 +1,29 @@
+---
+name: gsd:explore
+description: Socratic ideation and idea routing — think through ideas before committing to plans
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Grep
+  - Glob
+  - Task
+  - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
+---
+<objective>
+Open-ended Socratic ideation session. Guides the developer through exploring an idea via
+probing questions, optionally spawns research, then routes outputs to the appropriate GSD
+artifacts (notes, todos, seeds, research questions, requirements, or new phases).
+
+Accepts an optional topic argument: `/gsd-explore authentication strategy`
+</objective>
+
+<execution_context>
+@references/workflows/explore.md
+</execution_context>
+
+<process>
+Execute the explore workflow from @references/workflows/explore.md end-to-end.
+</process>

package/.agent/skills/gsd/references/commands/project/import.md

@@ -0,0 +1,38 @@
+---
+name: gsd:import
+description: Ingest external plans with conflict detection against project decisions before writing anything.
+argument-hint: "--from <filepath>"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - Task
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
+---
+
+<objective>
+Import external plan files into the GSD planning system with conflict detection against PROJECT.md decisions.
+
+- **--from**: Import an external plan file, detect conflicts, write as GSD PLAN.md, validate via gsd-plan-checker.
+
+Future: `--prd` mode for PRD extraction is planned for a follow-up PR.
+</objective>
+
+<execution_context>
+@references/workflows/import.md
+@references/docs/ui-brand.md
+@references/docs/gate-prompts.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+</context>
+
+<process>
+Execute the import workflow end-to-end.
+</process>

package/.agent/skills/gsd/references/commands/project/intel.md

@@ -0,0 +1,181 @@
+---
+name: gsd:intel
+description: "Query, inspect, or refresh codebase intelligence files in .planning/intel/"
+argument-hint: "[query <term>|status|diff|refresh]"
+allowed-tools:
+  - Read
+  - Bash
+  - Task
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
+---
+
+**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Antigravity's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.**
+
+## Step 0 -- Banner
+
+**Before ANY tool calls**, display this banner:
+
+```
+GSD > INTEL
+```
+
+Then proceed to Step 1.
+
+## Step 1 -- Config Gate
+
+Check if intel is enabled by reading `.planning/config.json` directly using the Read tool.
+
+**DO NOT use the gsd-tools config get-value command** -- it hard-exits on missing keys.
+
+1. Read `.planning/config.json` using the Read tool
+2. If the file does not exist: display the disabled message below and **STOP**
+3. Parse the JSON content. Check if `config.intel && config.intel.enabled === true`
+4. If `intel.enabled` is NOT explicitly `true`: display the disabled message below and **STOP**
+5. If `intel.enabled` is `true`: proceed to Step 2
+
+**Disabled message:**
+
+```
+GSD > INTEL
+
+Intel system is disabled. To activate:
+
+.agent/skills/gsd/bin/gsd-tools.cjs config-set intel.enabled true
+
+Then run /gsd-intel refresh to build the initial index.
+```
+
+---
+
+## Step 2 -- Parse Argument
+
+Parse `$ARGUMENTS` to determine the operation mode:
+
+| Argument | Action |
+|----------|--------|
+| `query <term>` | Run inline query (Step 2a) |
+| `status` | Run inline status check (Step 2b) |
+| `diff` | Run inline diff check (Step 2c) |
+| `refresh` | Spawn intel-updater agent (Step 3) |
+| No argument or unknown | Show usage message |
+
+**Usage message** (shown when no argument or unrecognized argument):
+
+```
+GSD > INTEL
+
+Usage: /gsd-intel <mode>
+
+Modes:
+  query <term>  Search intel files for a term
+  status        Show intel file freshness and staleness
+  diff          Show changes since last snapshot
+  refresh       Rebuild all intel files from codebase analysis
+```
+
+### Step 2a -- Query
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs intel query <term>
+```
+
+Parse the JSON output and display results:
+- If the output contains `"disabled": true`, display the disabled message from Step 1 and **STOP**
+- If no matches found, display: `No intel matches for '<term>'. Try /gsd-intel refresh to build the index.`
+- Otherwise, display matching entries grouped by intel file
+
+**STOP** after displaying results. Do not spawn an agent.
+
+### Step 2b -- Status
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs intel status
+```
+
+Parse the JSON output and display each intel file with:
+- File name
+- Last `updated_at` timestamp
+- STALE or FRESH status (stale if older than 24 hours or missing)
+
+**STOP** after displaying status. Do not spawn an agent.
+
+### Step 2c -- Diff
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs intel diff
+```
+
+Parse the JSON output and display:
+- Added entries since last snapshot
+- Removed entries since last snapshot
+- Changed entries since last snapshot
+
+If no snapshot exists, suggest running `refresh` first.
+
+**STOP** after displaying diff. Do not spawn an agent.
+
+---
+
+## Step 3 -- Refresh (Agent Spawn)
+
+Display before spawning:
+
+```
+GSD > Spawning intel-updater agent to analyze codebase...
+```
+
+Spawn a Task:
+
+```
+Task(
+  description="Refresh codebase intelligence files",
+  prompt="You are the gsd-intel-updater agent. Your job is to analyze this codebase and write/update intelligence files in .planning/intel/.
+
+Project root: ${CWD}
+.agent/skills/gsd/bin/gsd-tools.cjs
+
+Instructions:
+1. Analyze the codebase structure, dependencies, APIs, and architecture
+2. Write JSON intel files to .planning/intel/ (stack.json, api-map.json, dependency-graph.json, file-roles.json, arch-decisions.json)
+3. Each file must have a _meta object with updated_at timestamp
+4. Use gsd-tools intel extract-exports <file> to analyze source files
+5. Use gsd-tools intel patch-meta <file> to update timestamps after writing
+6. Use gsd-tools intel validate to check your output
+
+When complete, output: ## INTEL UPDATE COMPLETE
+If something fails, output: ## INTEL UPDATE FAILED with details."
+)
+```
+
+Wait for the agent to complete.
+
+---
+
+## Step 4 -- Post-Refresh Summary
+
+After the agent completes, run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs intel status
+```
+
+Display a summary showing:
+- Which intel files were written or updated
+- Last update timestamps
+- Overall health of the intel index
+
+---
+
+## Anti-Patterns
+
+1. DO NOT spawn an agent for query/status/diff operations -- these are inline CLI calls
+2. DO NOT modify intel files directly -- the agent handles writes during refresh
+3. DO NOT skip the config gate check
+4. DO NOT use the gsd-tools config get-value CLI for the config gate -- it exits on missing keys

package/.agent/skills/gsd/references/commands/{gsd-list-workspaces.md → project/list-workspaces.md}

@@ -1,11 +1,12 @@
 ---
-name: gsd-list-workspaces
-description: "List active GSD workspaces and their status"
+name: gsd:list-workspaces
+description: List active GSD workspaces and their status
 allowed-tools:
   - Bash
   - Read
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <objective>
 Scan `~/gsd-workspaces/` for workspace directories containing `WORKSPACE.md` manifests. Display a summary table with name, path, repo count, strategy, and GSD project status.
 </objective>

package/.agent/skills/gsd/references/commands/{gsd-map-codebase.md → project/map-codebase.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-map-codebase
-description: "Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents"
+name: gsd:map-codebase
+description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
 argument-hint: "[optional: specific area to map, e.g., 'api' or 'auth']"
 allowed-tools:
   - Read
@@ -9,9 +9,10 @@ allowed-tools:
   - Grep
   - Write
   - Task
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
 
-
 <objective>
 Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.
 

package/.agent/skills/gsd/references/commands/{gsd-new-project.md → project/new-project.md}

@@ -1,6 +1,6 @@
 ---
-name: gsd-new-project
-description: "Initialize a new project with deep context gathering and PROJECT.md"
+name: gsd:new-project
+description: Initialize a new project with deep context gathering and PROJECT.md
 argument-hint: "[--auto]"
 allowed-tools:
   - Read
@@ -8,8 +8,9 @@ allowed-tools:
   - Write
   - Task
   - AskUserQuestion
+gsd-source-version: 1.34.2
+migration-date: 2026-04-08
 ---
-
 <runtime_note>
 **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API.
 </runtime_note>