godpowers 2.7.0 → 3.0.1

package/skills/god-refactor.md

@@ -144,6 +144,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-repair.md

@@ -66,6 +66,4 @@ Built-in. Reads + writes:
 Calls into `lib/drift-detector.js`, `lib/code-scanner.js`, `lib/reverse-sync.js`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-repo.md

@@ -34,6 +34,4 @@ Suggested next: /god-build (start building the first milestone)
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-restore.md

@@ -75,6 +75,4 @@ files back via standard fs operations. Calls `/god-scan` after restore
 to refresh linkage map.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-roadmap-check.md

@@ -2,6 +2,7 @@
 name: god-roadmap-check
 deprecated: true
 replacement: god-reconcile
+successor: god-reconcile
 description: |
   Check if user intent overlaps with the existing ROADMAP.md before doing
   feature work. Returns: already-done, in-progress, enhancement,
@@ -17,12 +18,13 @@ description: |
 Deprecated: prefer `/god-reconcile` for new workflows. This command remains in
 the full profile for backward compatibility with existing route references.
 
-Reconcile intent against ROADMAP.md before adding work.
+Reconcile intent against ROADMAP.md before adding work. This legacy command
+delegates to `god-reconciler` with ROADMAP-focused output.
 
 ## Setup
 
 1. Verify `.godpowers/roadmap/ROADMAP.md` exists. If not: nothing to reconcile against; suggest /god-roadmap or /god-feature directly.
-2. Spawn god-roadmap-reconciler with the user's intent description and the roadmap path.
+2. Spawn `god-reconciler` with the user's intent description and ask for ROADMAP-focused output.
 
 ## Output
 
@@ -58,7 +60,7 @@ For each status, the recommendation differs:
 
 ## Verification
 
-After god-roadmap-reconciler returns:
+After `god-reconciler` returns:
 1. Verify the verdict has a status from the canonical 6
 2. Verify recommendation has a concrete action
 3. Display to user; await decision before proceeding

package/skills/god-roadmap.md

@@ -62,6 +62,4 @@ The reflog records every god-roadmap invocation as `op:god-roadmap` for `/god-un
   for `/god-repair` review. Re-running picks up cleanly.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-rollback.md

@@ -72,6 +72,4 @@ Writes via `lib/reverse-sync.js` (for linkage truncation) and standard
 fs operations (for artifact move).
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-scan.md

@@ -114,6 +114,4 @@ User content outside fences is never modified.
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-ship.md

@@ -0,0 +1,44 @@
+---
+name: god-ship
+description: |
+  Ship verb dispatcher. Routes release, deploy, observability, and launch
+  closure intent to existing deploy, observe, and launch leaf commands.
+
+  Triggers on: "god ship", "/god-ship", "ship this", "deploy this",
+  "launch this", "wire observability"
+---
+
+# /god-ship
+
+Route shipping intent to the smallest existing shipping command.
+
+## Runtime module resolution
+
+Resolve the Godpowers runtime root before inspecting routes:
+
+1. If `<projectRoot>/routing/god-deploy.yaml` exists, use the repository checkout runtime at `<projectRoot>`.
+2. Otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`.
+3. Read routing metadata from `<runtimeRoot>/routing/`.
+
+## Dispatch
+
+| Signal | Hand off to |
+|---|---|
+| `deploy`, `pipeline`, `environment` | `/god-deploy` |
+| `observe`, `observability`, `slo`, `alert`, `runbook` | `/god-observe` |
+| `launch`, `release copy`, `go live` | `/god-launch` |
+
+Default to `/god-deploy` when no stronger signal exists.
+
+## Process
+
+1. Select the target leaf command from the table.
+2. Read the selected leaf route YAML so prerequisites and next-step metadata stay source-controlled.
+3. Show the selected command, the matched signal, and the release gate implied by that leaf.
+4. Hand off to the selected leaf command after user confirmation.
+
+## Guardrails
+
+- Do not publish, tag, deploy, or create release notes directly from this dispatcher.
+- Do not bypass safe-sync, harden, or launch prerequisites from the selected route.
+- Keep deploy, observe, and launch callable as direct shortcuts.

package/skills/god-skip.md

@@ -62,6 +62,4 @@ Reverse a previous skip. Marks the sub-step `pending` again.
 Built-in. Reads and writes `state.json`, regenerates the managed progress view, and appends to reflog.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-stack.md

@@ -59,6 +59,4 @@ The reflog records every god-stack invocation as `op:god-stack` for `/god-undo`.
   for `/god-repair` review. Re-running picks up cleanly.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-status.md

@@ -4,7 +4,8 @@ description: |
   Re-derive project state from disk. Never from memory. Scans all artifact
   paths and reports what exists, what passes, and what's missing.
 
-  Triggers on: "god status", "where are we", "project status", "what's done"
+  Triggers on: "god status", "where are we", "project status", "what's done",
+  "god status --locate", "god status --lifecycle"
 ---
 
 # God Status
@@ -20,11 +21,13 @@ proactive checks, blockers, planning visibility, and the next action first.
 |------|----------|---------|
 | Overview | `/god-status` | Operational state, proactive checks, and blockers. |
 | Progress ledger | `/god-progress` | Requirement and roadmap increment completion. |
-| Lifecycle phase | `/god-lifecycle` | Project phase and fitting workflows. |
-| Resume location | `/god-locate` | Orientation from checkpoint, handoff, and disk state. |
+| Lifecycle phase | `/god-status --lifecycle` | Project phase and fitting workflows. |
+| Resume location | `/god-status --locate` | Orientation from checkpoint, handoff, and disk state. |
 | Next action | `/god-next` | Single recommended command with reason. |
 
-`/god-lifecycle` remains separate because it answers phase and workflow-fit questions without the full dashboard. `/god-locate` remains separate because it is optimized for fresh-session resume from CHECKPOINT.md, handoff files, and disk state.
+`/god-lifecycle` and `/god-locate` remain callable as full-profile compatibility
+aliases for one minor release. New workflows should use `/god-status
+--lifecycle` and `/god-status --locate`.
 
 ## Process
 
@@ -32,10 +35,12 @@ proactive checks, blockers, planning visibility, and the next action first.
 2. Resolve the runtime root and load `<runtimeRoot>/lib/dashboard.js`.
 3. Call `dashboard.compute(projectRoot)` and render with `dashboard.render(result)`.
 4. Prefer the MCP `status` tool when it is available, and fall back to the CLI or runtime module when it is not.
-5. Use `.godpowers/PROGRESS.md` only as generated fallback or legacy explanation when state.json is missing.
-6. Scan canonical artifact paths for PRD, design, architecture, roadmap, stack, repo, build, deploy, observe, launch, harden, sync, checkpoint, and requirements evidence.
-7. Compare disk state to recorded state and flag phantom resume or untracked work.
-8. Offer `/god-repair` when recorded state and disk evidence conflict.
+5. If `--lifecycle` is present, emphasize lifecycle phase, fitting workflows, PRD visibility, roadmap visibility, and the next route.
+6. If `--locate` is present, emphasize CHECKPOINT.md, HANDOFF.md, recent events, current step, and the next route.
+7. Use `.godpowers/PROGRESS.md` only as generated fallback or legacy explanation when state.json is missing.
+8. Scan canonical artifact paths for PRD, design, architecture, roadmap, stack, repo, build, deploy, observe, launch, harden, sync, checkpoint, and requirements evidence.
+9. Compare disk state to recorded state and flag phantom resume or untracked work.
+10. Offer `/god-repair` when recorded state and disk evidence conflict.
 
 ## Required reference
 

package/skills/god-story-build.md

@@ -60,6 +60,4 @@ Reverse-sync writes Implementation Linkage footer to ROADMAP.md
   still fires)
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story-close.md

@@ -66,6 +66,4 @@ linkage updates.
 - Trigger any other workflow automatically
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story.md

@@ -39,6 +39,4 @@ Add a new story under `.godpowers/stories/<feature-slug>/`.
 - `/god-stories` to see all stories
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-sync.md

@@ -43,7 +43,7 @@ User runs `/god-sync` after manual changes. Useful for:
    payload, agent handoffs, workflow metadata, recipe routes, extension packs,
    route quality, recipe coverage, release surfaces, and release policy are
    checked before sync closes. Structural drift should recommend scoped agents
-   such as `god-auditor`, `god-roadmap-reconciler`, `god-coordinator`, or
+   such as `god-auditor`, `god-reconciler`, `god-coordinator`, or
    `god-docs-writer`.
 6. If repo documentation changed durable project truth, plan or apply Pillars
    updates through `lib/pillars.planArtifactSync` or
@@ -94,7 +94,7 @@ Sync status:
     + 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 typed route outcomes, no-op, or recommended god-auditor>
-    + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-roadmap-reconciler>
+    + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-reconciler>
     + release-surface-sync: <checked badges/changelog/release/package guards, no-op, or recommended god-docs-writer>
     + pillars-sync: <updated N pillar files, no-op, or proposed>
     + checkpoint-sync: <CHECKPOINT.md updated or skipped>
@@ -154,6 +154,4 @@ Both bookends run automatically in feature-addition recipes. Both can be
 invoked manually for spot-checks.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-undo.md

@@ -52,6 +52,4 @@ Suggested next:
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-update-deps.md

@@ -120,6 +120,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-upgrade.md

@@ -123,6 +123,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-version.md

@@ -16,7 +16,7 @@ Print version and a short capability summary.
 ```
 Godpowers v2.3.1
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 112 skills, 40 agents, 13 workflows, 42 recipes
+Surface: 117 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