godpowers 2.2.1 → 2.3.1

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/routing/god-stack.yaml

@@ -30,7 +30,7 @@ standards:
   gate-on-failure: pause-for-user
 
 success-path:
-  next-recommended: /god-design
+  next-recommended: /god-repo
   conditional-next:
     - condition: ui-detected
       next: /god-design

package/routing/recipes/add-feature-mid-arc-pause.yaml

@@ -11,6 +11,12 @@ triggers:
     - "mid development"
     - "pause arc"
     - "feature during build"
+    - "add a feature"
+    - "feature addition"
+    - "add a feature during the current project run"
+    - "add a feature without breaking the current project run"
+    - "without breaking current project run"
+    - "do not disturb current work"
   state-conditions:
     - "lifecycle-phase == in-arc"
 

package/routing/recipes/brownfield-onboarding.yaml

@@ -11,6 +11,9 @@ triggers:
     - "inherit codebase"
     - "legacy code"
     - "understand existing"
+    - "audit an existing repo"
+    - "audit existing repo"
+    - "audit existing codebase"
   state-conditions:
     - "has-package-json"
 
@@ -24,10 +27,10 @@ sequences:
         why: "Deep history, decisions, conventions, risks"
       - command: "/god-reconstruct"
         why: "Reverse-engineer PRD/ARCH/ROADMAP/STACK from code"
-      - command: "/god-tech-debt"
-        why: "Categorize and prioritize debt"
       - command: "/god-audit"
         why: "Score reconstructed artifacts"
+      - command: "/god-tech-debt"
+        why: "Categorize and prioritize debt"
       - command: "/god-feature"
         why: "Now safe to add new work with reconciliation"
 

package/routing/recipes/extension-authoring.yaml

@@ -0,0 +1,32 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: extension-authoring
+  category: extension
+  description: "Create, test, install, and verify a Godpowers extension pack"
+
+triggers:
+  intent-keywords:
+    - "create extension pack"
+    - "create an extension pack"
+    - "author extension pack"
+    - "new extension pack"
+    - "scaffold extension"
+    - "build extension pack"
+    - "extend godpowers"
+    - "make a pack"
+
+sequences:
+  default:
+    description: "Create, test, install, and verify a Godpowers extension pack"
+    steps:
+      - command: "/god-extension-scaffold --name=@godpowers/my-pack --output=."
+        why: "Create the manifest, package, README, skill, and optional agent or workflow skeleton"
+      - command: "/god-test-extension <pack-dir>"
+        why: "Run contract tests before install or publish"
+      - command: "/god-extension-add <pack-dir>"
+        why: "Install the passing pack into the active runtime"
+      - command: "/god-extension-list"
+        why: "Verify the installed pack appears with its provided commands"
+
+default-sequence: default

package/routing/recipes/greenfield-fast.yaml

@@ -12,6 +12,9 @@ triggers:
     - "greenfield"
     - "new project"
     - "idea to production"
+    - "start a product"
+    - "start product"
+    - "build a product"
   state-conditions:
     - "no-godpowers-dir"
 

package/routing/recipes/production-broken.yaml

@@ -8,6 +8,10 @@ metadata:
 triggers:
   intent-keywords:
     - "production down"
+    - "production is broken"
+    - "production broken"
+    - "fix production"
+    - "prod is broken"
     - "urgent"
     - "p0"
     - "p1"

package/routing/recipes/release-maintenance.yaml

@@ -12,6 +12,9 @@ triggers:
     - "update readme badge"
     - "release notes"
     - "package release"
+    - "ship a release"
+    - "release the project"
+    - "prepare release"
 
 sequences:
   default:

package/routing/recipes/returning-after-break.yaml

@@ -11,6 +11,9 @@ triggers:
     - "after break"
     - "pick up where left"
     - "resume project"
+    - "coming back after a week"
+    - "back after a week"
+    - "coming back"
   state-conditions:
     - "file:.godpowers/PROGRESS.md"
 

package/routing/recipes/weekly-health-check.yaml

@@ -11,6 +11,8 @@ triggers:
     - "health check"
     - "hygiene"
     - "project health"
+    - "maintain project health"
+    - "maintain health"
   state-conditions:
     - "lifecycle-phase == steady-state-active"
 

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-discuss.md

@@ -11,7 +11,7 @@ description: |
 
 # /god-discuss
 
-Pre-planning Socratic discussion with domain grilling.
+Pre-planning Socratic discussion with domain and plan grilling.
 
 ## When to use
 
@@ -31,10 +31,15 @@ The agent:
 4. Explores the codebase instead of asking when repo evidence can answer
 5. Challenges vague, overloaded, or conflicting terms against the glossary
 6. Stress-tests domain relationships with concrete scenarios and edge cases
-7. Surfaces 2-3 hidden assumptions
-8. Identifies what's [DECISION] vs [HYPOTHESIS] vs [OPEN QUESTION]
-9. Drafts a brief in `.godpowers/discussions/<topic>.md`
-10. Updates `.godpowers/domain/GLOSSARY.md` when a term or ambiguity is resolved
+7. Attempts to falsify the proposed plan before accepting it:
+   - What breaks if the smallest happy path is wrong?
+   - Which dependency, user behavior, or edge case could invalidate the plan?
+   - What would make this scope too broad for one safe slice?
+   - What evidence would change the recommended next command?
+8. Surfaces 2-3 hidden assumptions
+9. Identifies what's [DECISION] vs [HYPOTHESIS] vs [OPEN QUESTION]
+10. Drafts a brief in `.godpowers/discussions/<topic>.md`
+11. Updates `.godpowers/domain/GLOSSARY.md` when a term or ambiguity is resolved
 
 The brief and glossary get passed to the next planning command. The glossary is
 preparation context, not a replacement for PRD, ARCH, ROADMAP, STACK, or Pillars

package/skills/god-doctor.md

@@ -48,9 +48,9 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 111 skills installed
+  [OK] 112 skills installed
   [OK] 40 agents installed
-  [OK] VERSION matches (2.2.1)
+  [OK] VERSION matches (2.3.1)
   [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
@@ -114,6 +114,12 @@ as a read-only diagnostic. It reports:
 `/god-doctor --fix` may call `lib/feature-awareness.run(projectRoot)` because
 that helper writes only safe state metadata and managed context fences.
 
+## Host Capability Reporting
+
+`/god-doctor` reports optional code intelligence when `ast-grep`, `sg`, or LSP
+tools are available. Missing code intelligence is diagnostic context only; it
+does not make the host degraded.
+
 ## Repo Documentation Sync
 
 For initialized projects, `/god-doctor` calls `lib/repo-doc-sync.detect` as a

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-extension-scaffold.md

@@ -0,0 +1,66 @@
+---
+name: god-extension-scaffold
+description: |
+  Create a publishable Godpowers extension pack skeleton from inside the
+  slash-command UX. Wraps the same extension authoring helper exposed by
+  `npx godpowers extension-scaffold`, then routes to contract testing.
+
+  Triggers on: "god extension scaffold", "/god-extension-scaffold",
+  "create extension pack", "author extension pack", "new extension pack",
+  "extend godpowers"
+---
+
+# /god-extension-scaffold
+
+Create a Godpowers extension pack skeleton.
+
+## Usage
+
+### `/god-extension-scaffold --name=@godpowers/my-pack --output=.`
+
+Optional arguments:
+
+- `--skill=custom-pack-command` sets the generated skill name.
+- `--agent=custom-pack-agent` creates a generated agent contract.
+- `--workflow=my-pack-workflow` creates a generated workflow YAML.
+- `--overwrite` allows replacing existing scaffold files.
+
+## Process
+
+1. Parse the requested package name, output root, optional skill, optional
+   agent, and optional workflow.
+2. Call `lib/extension-authoring.js scaffold(...)`.
+3. Validate the generated `manifest.yaml` against the extension manifest
+   contract.
+4. Report the created pack path and written files.
+5. Suggest `/god-test-extension <pack-dir>` before install or publish.
+
+## Output
+
+```
+Extension scaffold created: ./godpowers-my-pack
+
+Written:
+  manifest.yaml
+  package.json
+  README.md
+  skills/custom-pack-command.md
+
+Suggested next: /god-test-extension ./godpowers-my-pack
+```
+
+## Implementation
+
+Built-in. Calls `lib/extension-authoring.js scaffold(...)`.
+
+The terminal equivalent remains:
+
+```bash
+npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.
+```
+
+## Related
+
+- `/god-test-extension <path>` - contract test the pack before install or publish
+- `/god-extension-add <path>` - install a passing pack
+- `/god-extension-list` - verify the pack is visible in the runtime

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,9 +14,9 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v2.2.1
+Godpowers v2.3.1
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 111 skills, 40 agents, 13 workflows, 41 recipes
+Surface: 112 skills, 40 agents, 13 workflows, 42 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync, quick proof, request trace, release hardening, maintenance hardening

package/skills/god.md

@@ -160,13 +160,11 @@ any destructive sequence executes.
 ```
 User: /god production is broken
 
-Match: production-broken (score: 30)
-What this does: P0 incident response with rollback-first triage
+Match: production-broken (score: 20)
+What this does: Production is broken now
 
 Sequence:
-  1. /god-hotfix     Spawn god-debugger for fast triage
-  2. /god-deploy     Push the fix once green
-  3. /god-postmortem Schedule the incident review
+  1. /god-hotfix     Skip planning, debug, fix with TDD, expedited deploy, schedule postmortem
 
 Run this sequence? (yes / show others / cancel)
 ```
@@ -174,15 +172,14 @@ Run this sequence? (yes / show others / cancel)
 ### Example 2: ambiguous intent (multiple matches)
 
 ```
-User: /god add a new feature
+User: /god parallel feature during build
 
-Top matches for "add a new feature":
+Top matches for "parallel feature during build":
 
-  1. add-feature-mid-arc-pause       (15)   Pause /god-mode, run feature, resume
-  2. add-feature-small               (10)   Lightweight feature, no project-run context
-  3. add-feature-next-milestone      (10)   Defer to next milestone
+  1. add-feature-mid-arc-pause       (10)   Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume
+  2. add-feature-parallel            (10)   Parallel feature, do not disrupt main work
 
-Pick one (1/2/3) or describe more specifically.
+Pick one (1/2) or describe more specifically.
 ```
 
 ### Example 3: state-driven (no text)

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.