gsd-antigravity-kit 2.0.1 → 2.1.0

package/.agent/skills/gsd/references/commands/misc/graphify.md

@@ -0,0 +1,203 @@
+---
+name: gsd:graphify
+description: "Build, query, and inspect the project knowledge graph in .planning/graphs/"
+argument-hint: "[build|query <term>|status|diff]"
+allowed-tools:
+  - Read
+  - Bash
+  - Task
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+
+**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.**
+
+.agent/skills/gsd/bin/gsd-tools.cjs graphify …` as documented in this command and in `docs/CLI-TOOLS.md`. Other tooling may still use `gsd-sdk query` where a handler exists.
+
+## Step 0 -- Banner
+
+**Before ANY tool calls**, display this banner:
+
+```
+GSD > GRAPHIFY
+```
+
+Then proceed to Step 1.
+
+## Step 1 -- Config Gate
+
+Check if graphify 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.graphify && config.graphify.enabled === true`
+4. If `graphify.enabled` is NOT explicitly `true`: display the disabled message below and **STOP**
+5. If `graphify.enabled` is `true`: proceed to Step 2
+
+**Disabled message:**
+
+```
+GSD > GRAPHIFY
+
+Knowledge graph is disabled. To activate:
+
+.agent/skills/gsd/bin/gsd-tools.cjs config-set graphify.enabled true
+
+Then run /gsd-graphify build to create the initial graph.
+```
+
+---
+
+## Step 2 -- Parse Argument
+
+Parse `$ARGUMENTS` to determine the operation mode:
+
+| Argument | Action |
+|----------|--------|
+| `build` | Spawn graphify-builder agent (Step 3) |
+| `query <term>` | Run inline query (Step 2a) |
+| `status` | Run inline status check (Step 2b) |
+| `diff` | Run inline diff check (Step 2c) |
+| No argument or unknown | Show usage message |
+
+**Usage message** (shown when no argument or unrecognized argument):
+
+```
+GSD > GRAPHIFY
+
+Usage: /gsd-graphify <mode>
+
+Modes:
+  build           Build or rebuild the knowledge graph
+  query <term>    Search the graph for a term
+  status          Show graph freshness and statistics
+  diff            Show changes since last build
+```
+
+### Step 2a -- Query
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs graphify 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 the output contains `"error"` field, display the error message and **STOP**
+- If no nodes found, display: `No graph matches for '<term>'. Try /gsd-graphify build to create or rebuild the graph.`
+- Otherwise, display matched nodes grouped by type, with edge relationships and confidence tiers (EXTRACTED/INFERRED/AMBIGUOUS)
+
+**STOP** after displaying results. Do not spawn an agent.
+
+### Step 2b -- Status
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs graphify status
+```
+
+Parse the JSON output and display:
+- If `exists: false`, display the message field
+- Otherwise show last build time, node/edge/hyperedge counts, and STALE or FRESH indicator
+
+**STOP** after displaying status. Do not spawn an agent.
+
+### Step 2c -- Diff
+
+Run:
+
+```bash
+.agent/skills/gsd/bin/gsd-tools.cjs graphify diff
+```
+
+Parse the JSON output and display:
+- If `no_baseline: true`, display the message field
+- Otherwise show node and edge change counts (added/removed/changed)
+
+If no snapshot exists, suggest running `build` twice (first to create, second to generate a diff baseline).
+
+**STOP** after displaying diff. Do not spawn an agent.
+
+---
+
+## Step 3 -- Build (Agent Spawn)
+
+Run pre-flight check first:
+
+```
+.agent/skills/gsd/bin/gsd-tools.cjs" graphify build)
+```
+
+If pre-flight returns `disabled: true` or `error`, display the message and **STOP**.
+
+If pre-flight returns `action: "spawn_agent"`, display:
+
+```
+GSD > Spawning graphify-builder agent...
+```
+
+Spawn a Task:
+
+```
+Task(
+  description="Build or rebuild the project knowledge graph",
+  prompt="You are the graphify-builder agent. Your job is to build or rebuild the project knowledge graph using the graphify CLI.
+
+Project root: ${CWD}
+.agent/skills/gsd/bin/gsd-tools.cjs
+
+## Instructions
+
+1. **Invoke graphify:**
+   Run from the project root:
+   ```
+   graphify . --update
+   ```
+   This builds the knowledge graph with SHA256 incremental caching.
+   Timeout: up to 5 minutes (or as configured via graphify.build_timeout).
+
+2. **Validate output:**
+   Check that graphify-out/graph.json exists and is valid JSON with nodes[] and edges[] arrays.
+   If graphify exited non-zero or graph.json is not parseable, output:
+   ## GRAPHIFY BUILD FAILED
+   Include the stderr output for debugging. Do NOT delete .planning/graphs/ -- prior valid graph remains available.
+
+3. **Copy artifacts to .planning/graphs/:**
+   ```
+   cp graphify-out/graph.json .planning/graphs/graph.json
+   cp graphify-out/graph.html .planning/graphs/graph.html
+   cp graphify-out/GRAPH_REPORT.md .planning/graphs/GRAPH_REPORT.md
+   ```
+   These three files are the build output consumed by query, status, and diff commands.
+
+4. **Write diff snapshot:**
+   ```
+.agent/skills/gsd/bin/gsd-tools.cjs\" graphify build snapshot
+   ```
+   This creates .planning/graphs/.last-build-snapshot.json for future diff comparisons.
+
+5. **Report build summary:**
+   ```
+.agent/skills/gsd/bin/gsd-tools.cjs\" graphify status
+   ```
+   Display the node count, edge count, and hyperedge count from the status output.
+
+When complete, output: ## GRAPHIFY BUILD COMPLETE with the summary counts.
+If something fails at any step, output: ## GRAPHIFY BUILD FAILED with details."
+)
+```
+
+Wait for the agent to complete.
+
+---
+
+## Anti-Patterns
+
+1. DO NOT spawn an agent for query/status/diff operations -- these are inline CLI calls
+2. DO NOT modify graph files directly -- the build agent handles writes
+3. DO NOT skip the config gate check
+4. DO NOT use gsd-tools config get-value for the config gate -- it exits on missing keys

package/.agent/skills/gsd/references/commands/misc/inbox.md

@@ -0,0 +1,40 @@
+---
+name: gsd:inbox
+description: Triage and review all open GitHub issues and PRs against project templates and contribution guidelines
+argument-hint: "[--issues] [--prs] [--label] [--close-incomplete] [--repo owner/repo]"
+allowed-tools:
+  - Read
+  - Bash
+  - Write
+  - Grep
+  - Glob
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+<objective>
+One-command triage of the project's GitHub inbox. Fetches all open issues and PRs,
+reviews each against the corresponding template requirements (feature, enhancement,
+bug, chore, fix PR, enhancement PR, feature PR), reports completeness and compliance,
+and optionally applies labels or closes non-compliant submissions.
+
+**Flow:** Detect repo → Fetch open issues + PRs → Classify each by type → Review against template → Report findings → Optionally act (label, comment, close)
+</objective>
+
+<execution_context>
+@references/workflows/inbox.md
+</execution_context>
+
+<context>
+**Flags:**
+- `--issues` — Review only issues (skip PRs)
+- `--prs` — Review only PRs (skip issues)
+- `--label` — Auto-apply recommended labels after review
+- `--close-incomplete` — Close issues/PRs that fail template compliance (with comment explaining why)
+- `--repo owner/repo` — Override auto-detected repository (defaults to current git remote)
+</context>
+
+<process>
+Execute the inbox workflow from @references/workflows/inbox.md end-to-end.
+Parse flags from arguments and pass to workflow.
+</process>

package/.agent/skills/gsd/references/commands/misc/next.md

@@ -7,8 +7,8 @@ allowed-tools:
   - Grep
   - Glob
   - SlashCommand
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Detect the current project state and automatically invoke the next logical GSD workflow step.
@@ -16,7 +16,9 @@ No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to det
 
 Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead.
 
-Supports `--force` flag to bypass safety gates (checkpoint, error state, verification failures).
+Supports `--force` flag to bypass safety gates (checkpoint, error state, verification failures, and prior-phase completeness scan).
+
+Before routing to the next step, scans all prior phases for incomplete work: plans that ran without producing summaries, verification failures without overrides, and phases where discussion happened but planning never ran. When incomplete work is found, shows a structured report and offers three options: defer the gaps to the backlog and continue, stop and resolve manually, or force advance without recording. When prior phases are clean, routes silently with no interruption.
 </objective>
 
 <execution_context>

package/.agent/skills/gsd/references/commands/misc/progress.md

@@ -1,14 +1,15 @@
 ---
 name: gsd:progress
-description: Check project progress, show context, and route to next action (execute or plan)
+description: Check project progress, show context, and route to next action (execute or plan). Use --forensic to append a 6-check integrity audit after the standard report.
+argument-hint: "[--forensic]"
 allowed-tools:
   - Read
   - Bash
   - Grep
   - Glob
   - SlashCommand
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Check project progress, summarize recent work and what's ahead, then intelligently route to the next action - either executing an existing plan or creating the next one.

package/.agent/skills/gsd/references/commands/misc/sketch-wrap-up.md

@@ -0,0 +1,33 @@
+---
+name: gsd:sketch-wrap-up
+description: Package sketch design findings into a persistent project skill for future build conversations
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+<objective>
+Curate sketch design findings and package them into a persistent project skill that Antigravity
+auto-loads when building the real UI. Also writes a summary to `.planning/sketches/` for
+project history. Output skill goes to `./.antigravity/skills/sketch-findings-[project]/` (project-local).
+</objective>
+
+<execution_context>
+@references/workflows/sketch-wrap-up.md
+@references/docs/ui-brand.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
+</runtime_note>
+
+<process>
+Execute the sketch-wrap-up workflow from @references/workflows/sketch-wrap-up.md end-to-end.
+Preserve all curation gates (per-sketch review, grouping approval, ANTIGRAVITY.md routing line).
+</process>

package/.agent/skills/gsd/references/commands/misc/sketch.md

@@ -0,0 +1,47 @@
+---
+name: gsd:sketch
+description: Rapidly sketch UI/design ideas using throwaway HTML mockups with multi-variant exploration
+argument-hint: "<design idea to explore> [--quick]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+<objective>
+Explore design directions through throwaway HTML mockups before committing to implementation.
+Each sketch produces 2-3 variants for comparison. Sketches live in `.planning/sketches/` and
+integrate with GSD commit patterns, state tracking, and handoff workflows.
+
+Does not require `/gsd-new-project` — auto-creates `.planning/sketches/` if needed.
+</objective>
+
+<execution_context>
+@references/workflows/sketch.md
+@references/docs/ui-brand.md
+@references/docs/sketch-theme-system.md
+@references/docs/sketch-interactivity.md
+@references/docs/sketch-tooling.md
+@references/docs/sketch-variant-patterns.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
+</runtime_note>
+
+<context>
+Design idea: $ARGUMENTS
+
+**Available flags:**
+- `--quick` — Skip mood/direction intake, jump straight to decomposition and building. Use when the design direction is already clear.
+</context>
+
+<process>
+Execute the sketch workflow from @references/workflows/sketch.md end-to-end.
+Preserve all workflow gates (intake, decomposition, variant evaluation, MANIFEST updates, commit patterns).
+</process>

package/.agent/skills/gsd/references/commands/misc/spec-phase.md

@@ -0,0 +1,64 @@
+---
+name: gsd:spec-phase
+description: Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.
+argument-hint: "<phase> [--auto] [--text]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+
+<objective>
+Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.
+
+**Position in workflow:** `spec-phase → discuss-phase → plan-phase → execute-phase → verify`
+
+**How it works:**
+1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
+2. Scout the codebase — understand current state before asking questions
+3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)
+4. Score ambiguity across 4 weighted dimensions after each round
+5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
+6. Commit SPEC.md — discuss-phase picks it up automatically on next run
+
+**Output:** `{phase_dir}/{padded_phase}-SPEC.md` — falsifiable requirements that lock "what/why" before discuss-phase handles "how"
+</objective>
+
+<execution_context>
+@references/workflows/spec-phase.md
+@assets/templates/spec.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent.
+</runtime_note>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+**Flags:**
+- `--auto` — Skip interactive questions; Antigravity selects recommended defaults and writes SPEC.md
+- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)
+
+Context files are resolved in-workflow using `init phase-op`.
+</context>
+
+<process>
+Execute the spec-phase workflow from @references/workflows/spec-phase.md end-to-end.
+
+**MANDATORY:** Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.
+</process>
+
+<success_criteria>
+- Codebase scouted for current state before questioning begins
+- All 4 ambiguity dimensions scored after each interview round
+- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
+- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
+- SPEC.md committed atomically
+- User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically
+</success_criteria>

package/.agent/skills/gsd/references/commands/misc/spike-wrap-up.md

@@ -0,0 +1,33 @@
+---
+name: gsd:spike-wrap-up
+description: Package spike findings into a persistent project skill for future build conversations
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+<objective>
+Curate spike experiment findings and package them into a persistent project skill that Antigravity
+auto-loads in future build conversations. Also writes a summary to `.planning/spikes/` for
+project history. Output skill goes to `./.antigravity/skills/spike-findings-[project]/` (project-local).
+</objective>
+
+<execution_context>
+@references/workflows/spike-wrap-up.md
+@references/docs/ui-brand.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
+</runtime_note>
+
+<process>
+Execute the spike-wrap-up workflow from @references/workflows/spike-wrap-up.md end-to-end.
+Preserve all curation gates (per-spike review, grouping approval, ANTIGRAVITY.md routing line).
+</process>

package/.agent/skills/gsd/references/commands/misc/spike.md

@@ -0,0 +1,43 @@
+---
+name: gsd:spike
+description: Rapidly spike an idea with throwaway experiments to validate feasibility before planning
+argument-hint: "<idea to validate> [--quick]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - AskUserQuestion
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
+---
+<objective>
+Rapid feasibility validation through focused, throwaway experiments. Each spike answers one
+specific question with observable evidence. Spikes live in `.planning/spikes/` and integrate
+with GSD commit patterns, state tracking, and handoff workflows.
+
+Does not require `/gsd-new-project` — auto-creates `.planning/spikes/` if needed.
+</objective>
+
+<execution_context>
+@references/workflows/spike.md
+@references/docs/ui-brand.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
+</runtime_note>
+
+<context>
+Idea: $ARGUMENTS
+
+**Available flags:**
+- `--quick` — Skip decomposition/alignment, jump straight to building. Use when you already know what to spike.
+</context>
+
+<process>
+Execute the spike workflow from @references/workflows/spike.md end-to-end.
+Preserve all workflow gates (decomposition, risk ordering, verification, MANIFEST updates, commit patterns).
+</process>

package/.agent/skills/gsd/references/commands/misc/verify-work.md

@@ -10,8 +10,8 @@ allowed-tools:
   - Edit
   - Write
   - Task
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Validate built features through conversational testing with persistent state.

package/.agent/skills/gsd/references/commands/phase/add-phase.md

@@ -6,8 +6,8 @@ allowed-tools:
   - Read
   - Write
   - Bash
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 
 <objective>

package/.agent/skills/gsd/references/commands/phase/add-tests.md

@@ -15,8 +15,8 @@ argument-instructions: |
   Parse the argument as a phase number (integer, decimal, or letter-suffix), plus optional free-text instructions.
   Example: /gsd-add-tests 12
   Example: /gsd-add-tests 12 focus on edge cases in the pricing module
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.

package/.agent/skills/gsd/references/commands/phase/discuss-phase.md

@@ -1,7 +1,7 @@
 ---
 name: gsd:discuss-phase
-description: Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Antigravity picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
-argument-hint: "<phase> [--auto] [--chain] [--batch] [--analyze] [--text] [--power]"
+description: Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Antigravity picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
+argument-hint: "<phase> [--all] [--auto] [--chain] [--batch] [--analyze] [--text] [--power]"
 allowed-tools:
   - Read
   - Write
@@ -12,8 +12,8 @@ allowed-tools:
   - Task
   - mcp__context7__resolve-library-id
   - mcp__context7__query-docs
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 
 <objective>
@@ -50,7 +50,7 @@ Context files are resolved in-workflow using `init phase-op` and roadmap/state t
 <process>
 **Mode routing:**
 ```bash
-.agent/skills/gsd/bin/gsd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
+DISCUSS_MODE=$(gsd-sdk query config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
 ```
 
 If `DISCUSS_MODE` is `"assumptions"`: Read and execute @references/workflows/discuss-phase-assumptions.md end-to-end.

package/.agent/skills/gsd/references/commands/phase/execute-phase.md

@@ -1,7 +1,7 @@
 ---
 name: gsd:execute-phase
 description: Execute all plans in a phase with wave-based parallelization
-argument-hint: "<phase-number> [--wave N] [--gaps-only] [--interactive]"
+argument-hint: "<phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd]"
 allowed-tools:
   - Read
   - Write
@@ -12,8 +12,8 @@ allowed-tools:
   - Task
   - TodoWrite
   - AskUserQuestion
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Execute all plans in a phase using wave-based parallel execution.
@@ -56,7 +56,7 @@ Phase: $ARGUMENTS
 - If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
 - Do not infer that a flag is active just because it is documented in this prompt
 
-Context files are resolved inside the workflow via `gsd-tools init execute-phase` and per-subagent `<files_to_read>` blocks.
+Context files are resolved inside the workflow via `gsd-sdk query init.execute-phase` and per-subagent `<files_to_read>` blocks.
 </context>
 
 <process>

package/.agent/skills/gsd/references/commands/phase/insert-phase.md

@@ -6,8 +6,8 @@ allowed-tools:
   - Read
   - Write
   - Bash
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 
 <objective>

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

@@ -7,8 +7,8 @@ allowed-tools:
   - Bash
   - Grep
   - Glob
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 
 <objective>

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

@@ -1,7 +1,7 @@
 ---
 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]"
+argument-hint: "[phase] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--prd <file>] [--reviews] [--text] [--tdd]"
 agent: gsd-planner
 allowed-tools:
   - Read
@@ -13,8 +13,8 @@ allowed-tools:
   - AskUserQuestion
   - WebFetch
   - mcp__context7__*
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.

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

@@ -7,8 +7,8 @@ allowed-tools:
   - Write
   - Bash
   - Glob
-gsd-source-version: 1.34.2
-migration-date: 2026-04-08
+gsd-source-version: 1.37.1
+migration-date: 2026-04-18
 ---
 <objective>
 Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.