godpowers 2.2.0 → 2.3.0

package/routing/god-migrate.yaml

@@ -2,7 +2,7 @@ apiVersion: godpowers/v1
 kind: CommandRouting
 metadata:
   command: /god-migrate
-  description: Detect and migrate GSD, BMAD, and Superpowers planning context
+  description: Detect and migrate legacy planning, BMAD, and Superpowers planning context
   tier: 0
 
 prerequisites:
@@ -16,7 +16,7 @@ execution:
   context: current
   reads:
     - .planning/**
-    - .gsd/**
+    - .legacy-planning/**
     - _bmad-output/**
     - .bmad/**
     - docs/superpowers/**
@@ -29,7 +29,7 @@ execution:
     - .godpowers/build/STATE.md
     - .godpowers/state.json
     - .planning/GODPOWERS-SYNC.md
-    - .gsd/GODPOWERS-SYNC.md
+    - .legacy-planning/GODPOWERS-SYNC.md
     - _bmad-output/GODPOWERS-SYNC.md
     - .bmad/GODPOWERS-SYNC.md
     - docs/superpowers/GODPOWERS-SYNC.md

package/schema/state.v1.json

@@ -108,7 +108,7 @@
         "properties": {
           "id": {
             "type": "string",
-            "enum": ["gsd", "bmad", "superpowers", "other"]
+            "enum": ["legacy-planning", "bmad", "superpowers", "other"]
           },
           "name": { "type": "string" },
           "confidence": {

package/skills/god-build.md

@@ -30,6 +30,19 @@ Orchestrate the build via specialist agents.
 Spawn **god-planner** in fresh context with ROADMAP, ARCH, DECISION.
 Output: `.godpowers/build/PLAN.md` with vertical slices grouped into waves.
 
+After the planner returns, run the source-grounding preflight from
+`lib/source-grounding.js` against `.godpowers/build/PLAN.md`. The plan must
+distinguish existing files, existing symbols, new artifacts, and unchecked
+references before any executor starts.
+
+Block execution when:
+- A plan cites an existing file that does not exist.
+- A plan cites an existing symbol that cannot be found in the repo.
+- A cited reference is neither grounded nor declared as a new artifact.
+
+Allow execution only when missing references are corrected, marked as new
+artifacts, or explicitly accepted by the user as unchecked risk.
+
 ### Phase 2: Execute Waves
 
 For each wave in PLAN.md:
@@ -59,9 +72,10 @@ After all waves:
 2. Run linter. All clean.
 3. Run the package's typecheck/check command when present. All pass.
 4. If any verification command fails, do not mark Build complete. Re-enter
-   repair mode with the owning agent, pass the exact failing diagnostics, rerun
-   the command, and repeat until green or until the same root failure survives
-   3 repair attempts.
+   repair mode with the owning agent. Classify the failure as retry,
+   decompose, prune, or escalate. Pass the exact failing diagnostics, rerun the
+   command, and repeat until green or until the same root failure exhausts the
+   repair budget.
 5. Update PROGRESS.md: Build status = done
 6. If the build plan or implementation establishes durable conventions, plan
    pillar updates through `lib/pillars.planArtifactSync`. Under

package/skills/god-doctor.md

@@ -50,7 +50,7 @@ GODPOWERS DOCTOR
 Install: claude (~/.claude/)
   [OK] 111 skills installed
   [OK] 40 agents installed
-  [OK] VERSION matches (2.2.0)
+  [OK] VERSION matches (2.3.0)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/
@@ -106,7 +106,7 @@ as a read-only diagnostic. It reports:
 - runtime version recorded in `state.json`
 - missing current Godpowers feature IDs
 - missing managed AI-tool context fences
-- unimported GSD, BMAD, or Superpowers evidence that should route to
+- unimported legacy planning, BMAD, or Superpowers evidence that should route to
   `/god-migrate`
 - `god-greenfieldifier` recommendation when migration evidence is low
   confidence or conflicting

package/skills/god-dogfood.md

@@ -16,7 +16,7 @@ Run deterministic messy-repo scenarios before release or after automation change
 
 - [DECISION] Use `/god-dogfood` before a release when migration, host autonomy,
   extension authoring, or Mode D suite release behavior changes.
-- [DECISION] Use `/god-dogfood` when a project already contains GSD, BMAD, or
+- [DECISION] Use `/god-dogfood` when a project already contains legacy planning, BMAD, or
   Superpowers context and you need confidence that Godpowers can import and
   sync back without deleting prior-system files.
 - [DECISION] Use `/god-dogfood` when host-spawn guarantees are unclear and the
@@ -44,7 +44,7 @@ npx godpowers dogfood --json
 
 ## Expected Coverage
 
-- [DECISION] The dogfood suite includes a half-migrated GSD project.
+- [DECISION] The dogfood suite includes a half-migrated legacy planning project.
 - [DECISION] The dogfood suite includes degraded and full host capability
   scenarios.
 - [DECISION] The dogfood suite includes extension scaffold validation.

package/skills/god-init.md

@@ -36,7 +36,7 @@ needs to specify a mode.
      command. This happens before `/god-prd`, `/god-next`, or `/god-mode`
      continues.
    - Look for adjacent planning-system context:
-     - GSD: `.gsd/`, `.planning/`, `GSD.md`, `gsd*.md`
+     - legacy planning: `.legacy-planning/`, `.planning/`, `LEGACY-PLANNING.md`, `legacy-planning*.md`
      - Superpowers: `.superpowers/`, `superpowers/`, `SUPERPOWERS.md`,
        `.claude/skills/`, `.codex/skills/`
      - BMAD: `.bmad-core/`, `bmad-core/`, `.bmad/`, `BMAD.md`,
@@ -45,7 +45,7 @@ needs to specify a mode.
      `.godpowers/prep/IMPORTED-CONTEXT.md` as preparation context.
      Do not treat external planning-system files as source of truth.
    - Auto-invoke `lib/planning-systems.importPlanningContext(projectRoot)`
-     when GSD, Superpowers, or BMAD context is detected. Report this as
+     when legacy planning, Superpowers, or BMAD context is detected. Report this as
      `Agent: none, local runtime only`.
    - If import confidence is low, more than one source system appears to
      conflict, or canonical Godpowers seed artifacts cannot be created from
@@ -57,7 +57,7 @@ needs to specify a mode.
      - UI surfaces: `src/components/`, `app/`, `pages/`, `routes/`,
        `public/`, form-heavy flows, dashboards, editor surfaces, mobile
        shells, marketing pages, or other user-facing product experience
-     - Imported GSD, Superpowers, or BMAD context that mentions UX, screens,
+     - Imported legacy planning, Superpowers, or BMAD context that mentions UX, screens,
        journeys, components, brand, interaction states, or visual design
    - Record the result in `INITIAL-FINDINGS.md` so `/god-prd`, `/god-next`,
      and `/god-mode` can place `/god-design` after PRD and before
@@ -114,7 +114,7 @@ needs to specify a mode.
    - Run Mode Detection (announced in plain English; stored as A/B/C/E internally)
    - Run Scale Detection (trivial/small/medium/large/enterprise)
    - Write `.godpowers/prep/INITIAL-FINDINGS.md`
-   - Run planning-system context detection for GSD, Superpowers, and BMAD
+   - Run planning-system context detection for legacy planning, Superpowers, and BMAD
    - Write `.godpowers/prep/IMPORTED-CONTEXT.md` when useful context exists
    - Run automatic planning-system import through
      `lib/planning-systems.importPlanningContext(projectRoot)` and record
@@ -153,7 +153,7 @@ needs to specify a mode.
      PROGRESS.md
      prep/
        INITIAL-FINDINGS.md
-       IMPORTED-CONTEXT.md   # only when GSD / Superpowers / BMAD context exists
+       IMPORTED-CONTEXT.md   # only when legacy planning / Superpowers / BMAD context exists
      prd/
      arch/
        adr/
@@ -194,7 +194,7 @@ shape, framework and tooling signals, tests, CI, docs, AI-tool files, detected
 methodology systems, Pillars health, UI or product-experience signals, risk
 signals, and the reasoning behind the suggested next command.
 
-If GSD, Superpowers, BMAD, or similar planning context is detected, create
+If legacy planning, Superpowers, BMAD, or similar planning context is detected, create
 `.godpowers/prep/IMPORTED-CONTEXT.md`. This artifact is preparation context,
 not source of truth. It feeds PRD, architecture, roadmap, and stack decisions
 as hypothesis-level input only.

package/skills/god-migrate.md

@@ -1,12 +1,12 @@
 ---
 name: god-migrate
 description: |
-  Detect GSD, BMAD, and Superpowers planning systems, migrate useful context
+  Detect legacy planning, BMAD, and Superpowers planning systems, migrate useful context
   into Godpowers prep and seed artifacts, and sync Godpowers progress back to
   the prior system through managed companion files.
 
-  Triggers on: "god migrate", "/god-migrate", "migrate from gsd",
-  "migrate from bmad", "migrate from superpowers", "sync back to gsd",
+  Triggers on: "god migrate", "/god-migrate", "migrate from legacy-planning",
+  "migrate from bmad", "migrate from superpowers", "sync back to legacy-planning",
   "sync back to bmad", "sync back to superpowers"
 ---
 
@@ -16,7 +16,7 @@ Detect and migrate adjacent planning systems into Godpowers.
 
 ## When To Use
 
-- A project already has GSD `.planning/` or `.gsd/` context.
+- A project already has legacy planning `.planning/` or `.legacy-planning/` context.
 - A project already has BMAD `_bmad/`, `_bmad-output/`, `.bmad-core/`, or
   `.bmad/` context.
 - A project already has Superpowers specs, plans, or project-local skills.
@@ -26,7 +26,7 @@ Detect and migrate adjacent planning systems into Godpowers.
 
 ## Auto-Invoke Contract
 
-`/god-init` auto-invokes the import path when it detects GSD, BMAD, or
+`/god-init` auto-invokes the import path when it detects legacy planning, BMAD, or
 Superpowers context. It must show this visible status card:
 
 ```
@@ -74,7 +74,7 @@ lib/planning-systems.importPlanningContext(projectRoot, {
 ```
 
 This:
-- detects GSD, BMAD, and Superpowers sources
+- detects legacy planning, BMAD, and Superpowers sources
 - writes `.godpowers/prep/IMPORTED-CONTEXT.md`
 - writes missing Godpowers seed artifacts when enough source evidence exists
 - marks those seed artifacts as `imported` in `state.json`
@@ -98,14 +98,14 @@ This:
 
 | Source system | Import evidence | Godpowers destination | Sync-back destination |
 |---|---|---|---|
-| GSD | `.planning/PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md`, phase files | prep context, PRD seed, roadmap seed, build-state seed | `.planning/GODPOWERS-SYNC.md` |
-| GSD 2 | `.gsd/` files | prep context and seeds when source files are readable | `.gsd/GODPOWERS-SYNC.md` |
+| legacy planning | `.planning/PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md`, phase files | prep context, PRD seed, roadmap seed, build-state seed | `.planning/GODPOWERS-SYNC.md` |
+| legacy planning variant | `.legacy-planning/` files | prep context and seeds when source files are readable | `.legacy-planning/GODPOWERS-SYNC.md` |
 | BMAD | `_bmad-output/planning-artifacts/PRD.md`, `architecture.md`, epics, stories, sprint status | prep context, PRD seed, arch seed, roadmap seed | `_bmad-output/GODPOWERS-SYNC.md` |
 | Superpowers | `docs/superpowers/specs/*.md`, `docs/superpowers/plans/*.md`, project-local skills | prep context, PRD seed, roadmap seed, build-state seed | `docs/superpowers/GODPOWERS-SYNC.md` |
 
 ## Guardrails
 
-- Do not delete, move, or rewrite GSD, BMAD, or Superpowers files.
+- Do not delete, move, or rewrite legacy planning, BMAD, or Superpowers files.
 - Do not treat imported content as authoritative until a Godpowers artifact or
   the user confirms it.
 - Do not write outside Godpowers-owned fences in source-system files.
@@ -120,7 +120,7 @@ This:
 Migration complete.
 
 Detected:
-  + GSD: high confidence, 12 files
+  + legacy planning: high confidence, 12 files
   + BMAD: not detected
   + Superpowers: medium confidence, 2 files
 

package/skills/god-sync.md

@@ -50,7 +50,7 @@ User runs `/god-sync` after manual changes. Useful for:
    `lib/pillars.applyArtifactSync` under the active Pillars policy.
 7. If `state.json` contains enabled `source-systems`, auto-invoke
    `lib/source-sync.run(projectRoot)` so current Godpowers progress is written
-   back to imported GSD, BMAD, or Superpowers companion files. Report this as
+   back to imported legacy planning, BMAD, or Superpowers companion files. Report this as
    `Agent: none, local runtime only`.
 8. Spawn god-updater in fresh context with:
    - The reconciliation verdict (if available from a prior /god-reconcile)
@@ -90,7 +90,7 @@ Sync status:
   Local syncs:
     + reverse-sync: <scanned N files, updated M footers, populated K review items>
     + feature-awareness: <recorded runtime features, refreshed context, or no-op>
-    + source-sync: <written GSD/BMAD/Superpowers companion files, no-op, or skipped>
+    + source-sync: <written legacy planning/BMAD/Superpowers companion files, no-op, or skipped>
     + repo-doc-sync: <refreshed README badges/counts, recommended god-docs-writer, or no-op>
     + repo-surface-sync: <checked routes/package/agents/workflows/extensions, recommended scoped agents, or no-op>
     + route-quality-sync: <checked atomic spawns and contextual exits, no-op, or recommended god-auditor>

package/skills/god-update-deps.md

@@ -34,8 +34,10 @@ The agent:
 1. Runs the appropriate audit tool for the stack (`npm audit`, `pip-audit`,
    etc.)
 2. Lists outdated and stale dependencies
-3. Classifies each: Critical CVE / Stale / Major behind / Minor behind / OK
-4. Writes AUDIT.md
+3. Runs package legitimacy checks for new replacement candidates before
+   recommending them
+4. Classifies each: Critical CVE / Stale / Major behind / Minor behind / OK
+5. Writes AUDIT.md
 
 ### Phase 2: Triage
 The agent presents the audit. Priority order:

package/skills/god-version.md

@@ -14,7 +14,7 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v2.2.0
+Godpowers v2.3.0
 Install: /Users/.../.claude/  (matches package.json)
 Surface: 111 skills, 40 agents, 13 workflows, 41 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1

package/templates/IMPORTED-CONTEXT.md

@@ -6,7 +6,7 @@
 
 ## Sources Detected
 
-- [DECISION] Source system: [GSD / Superpowers / BMAD / other].
+- [DECISION] Source system: [legacy planning / Superpowers / BMAD / other].
 - [DECISION] Source path: [relative path].
 - [DECISION] Managed sync-back path: [relative path or "not enabled"].
 - [HYPOTHESIS] Useful signal: [what this source appears to clarify].

package/templates/INITIAL-FINDINGS.md

@@ -24,7 +24,7 @@
 ## Methodology And AI Tool Signals
 
 - [HYPOTHESIS] AI instruction files found: [paths or "none detected"].
-- [HYPOTHESIS] GSD context found: [paths or "none detected"].
+- [HYPOTHESIS] Legacy planning context found: [paths or "none detected"].
 - [HYPOTHESIS] Superpowers context found: [paths or "none detected"].
 - [HYPOTHESIS] BMAD context found: [paths or "none detected"].
 - [HYPOTHESIS] Pillars context health: [present / partial / initialized].
@@ -56,6 +56,6 @@
 - [DECISION] Downstream agents may use this artifact as preparation context only.
 - [DECISION] If this artifact conflicts with `.godpowers/intent.yaml`, `.godpowers/state.json`, `PROGRESS.md`, or a completed Godpowers artifact, the Godpowers artifact wins.
 - [DECISION] Pillars files under `agents/*.md` are the native project context layer for Godpowers commands.
-- [DECISION] Imported GSD, Superpowers, and BMAD signals must be converted into Godpowers-native artifacts, not preserved as parallel state.
+- [DECISION] Imported legacy planning, Superpowers, and BMAD signals must be converted into Godpowers-native artifacts, not preserved as parallel state.
 - [DECISION] Managed sync-back files may be written only by Godpowers-owned fences or companion paths.
 - [DECISION] Host capability and dogfood findings inform routing, but completed Godpowers artifacts remain authoritative.