godpowers 2.6.0 → 3.0.0

package/routing/god-design.yaml

@@ -8,7 +8,7 @@ metadata:
 
 prerequisites:
   required:
-    - check: file:.godpowers/PROGRESS.md
+    - check: state:initialized == true
       reason: "/god-design needs an initialized project"
       auto-complete: /god-init
     - check: file:.godpowers/prd/PRD.md
@@ -37,7 +37,7 @@ execution:
   writes:
     - DESIGN.md
     - PRODUCT.md
-    - .godpowers/design/STATE.md
+    - .godpowers/state.json
 
 standards:
   have-nots:

package/routing/god-extend.yaml

@@ -0,0 +1,47 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-extend
+  description: Extend verb dispatcher
+  tier: 0
+  family: extend
+
+prerequisites:
+  required: []
+
+execution:
+  spawns: [built-in]
+  context: fresh
+  reads:
+    - routing/god-extension-scaffold.yaml
+    - routing/god-extension-add.yaml
+    - routing/god-extension-list.yaml
+    - routing/god-extension-info.yaml
+    - routing/god-extension-remove.yaml
+    - routing/god-test-extension.yaml
+    - routing/god-build-agent.yaml
+  writes: []
+
+dispatch:
+  scaffold: /god-extension-scaffold
+  add: /god-extension-add
+  list: /god-extension-list
+  info: /god-extension-info
+  remove: /god-extension-remove
+  test: /god-test-extension
+  agent: /god-build-agent
+
+success-path:
+  next-recommended: varies
+  outcome:
+    type: contextual
+    label: Extend dispatch route
+    reason: The next route depends on the requested extension operation.
+    allowed-next: [/god-extension-scaffold, /god-extension-add, /god-extension-list, /god-extension-info, /god-extension-remove, /god-test-extension, /god-build-agent]
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: no direct state update; selected leaf command owns state
+  events: [agent.start, decision.route, agent.end]

package/routing/god-fix.yaml

@@ -0,0 +1,37 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-fix
+  description: Fix verb dispatcher
+  tier: 0
+  family: build
+
+prerequisites:
+  required: []
+
+execution:
+  spawns: [built-in]
+  context: fresh
+  reads:
+    - routing/god-debug.yaml
+    - routing/god-hotfix.yaml
+  writes: []
+
+dispatch:
+  debug: /god-debug
+  hotfix: /god-hotfix
+
+success-path:
+  next-recommended: varies
+  outcome:
+    type: contextual
+    label: Fix dispatch route
+    reason: The next route depends on whether production urgency is present.
+    allowed-next: [/god-debug, /god-hotfix]
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: no direct state update; selected leaf command owns state
+  events: [agent.start, decision.route, agent.end]

package/routing/god-launch.yaml

@@ -22,7 +22,10 @@ execution:
   spawns: [god-launch-strategist]
   context: fresh
   writes:
-    - .godpowers/launch/STATE.md
+    - .godpowers/state.json
+    - landing copy
+    - OG cards
+    - launch runbook
 
 standards:
   substitution-test: true

package/routing/god-lifecycle.yaml

@@ -4,7 +4,7 @@ metadata:
   command: /god-lifecycle
   description: Show project phase
   tier: 0
-  family: continue
+  family: compatibility
   trigger-precedence:
     - trigger: where am i
       prefer: /god-locate

package/routing/god-locate.yaml

@@ -4,7 +4,7 @@ metadata:
   command: /god-locate
   description: 
   tier: 0
-  family: continue
+  family: compatibility
 
 prerequisites:
   required: []

package/routing/god-migrate.yaml

@@ -27,7 +27,6 @@ execution:
     - .godpowers/arch/ARCH.md
     - .godpowers/roadmap/ROADMAP.md
     - .godpowers/stack/DECISION.md
-    - .godpowers/build/STATE.md
     - .godpowers/state.json
     - .planning/GODPOWERS-SYNC.md
     - .legacy-planning/GODPOWERS-SYNC.md

package/routing/god-mode.yaml

@@ -8,7 +8,7 @@ metadata:
 
 prerequisites:
   required:
-    - check: file:.godpowers/PROGRESS.md OR mode-A-greenfield
+    - check: state:initialized == true OR mode-A-greenfield
       auto-complete: /god-init
       human-required: true
     - check: safe-sync-clear

package/routing/god-observe.yaml

@@ -19,7 +19,10 @@ execution:
   spawns: [god-observability-engineer]
   context: fresh
   writes:
-    - .godpowers/observe/STATE.md
+    - .godpowers/state.json
+    - alert definitions
+    - dashboard definitions
+    - runbooks
 
 standards:
   substitution-test: true

package/routing/god-plan.yaml

@@ -0,0 +1,45 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-plan
+  description: Planning verb dispatcher
+  tier: 0
+  family: start
+
+prerequisites:
+  required: []
+
+execution:
+  spawns: [built-in]
+  context: fresh
+  reads:
+    - routing/god-prd.yaml
+    - routing/god-design.yaml
+    - routing/god-arch.yaml
+    - routing/god-roadmap.yaml
+    - routing/god-stack.yaml
+    - routing/god-reconstruct.yaml
+  writes: []
+
+dispatch:
+  prd: /god-prd
+  design: /god-design
+  arch: /god-arch
+  roadmap: /god-roadmap
+  stack: /god-stack
+  reconstruct: /god-reconstruct
+
+success-path:
+  next-recommended: varies
+  outcome:
+    type: contextual
+    label: Planning dispatch route
+    reason: The next route depends on the requested planning artifact.
+    allowed-next: [/god-prd, /god-design, /god-arch, /god-roadmap, /god-stack, /god-reconstruct]
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: no direct state update; selected leaf command owns state
+  events: [agent.start, decision.route, agent.end]

package/routing/god-prd.yaml

@@ -8,7 +8,7 @@ metadata:
 
 prerequisites:
   required:
-    - check: file:.godpowers/PROGRESS.md
+    - check: state:initialized == true
       auto-complete: /god-init
       human-required: true
   recommended:

package/routing/god-reconcile.yaml

@@ -8,7 +8,7 @@ metadata:
 
 prerequisites:
   required:
-    - check: file:.godpowers/PROGRESS.md
+    - check: state:initialized == true
       auto-complete: /god-init
       human-required: true
 
@@ -21,11 +21,8 @@ execution:
     - .godpowers/roadmap/ROADMAP.md
     - .godpowers/stack/DECISION.md
     - .godpowers/repo/AUDIT.md
-    - .godpowers/build/STATE.md
-    - .godpowers/deploy/STATE.md
-    - .godpowers/observe/STATE.md
+    - .godpowers/state.json
     - .godpowers/harden/FINDINGS.md
-    - .godpowers/launch/STATE.md
     - .godpowers/backlog/BACKLOG.md
     - .godpowers/seeds/
     - .godpowers/todos/TODOS.md

package/routing/god-ship.yaml

@@ -0,0 +1,39 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-ship
+  description: Ship verb dispatcher
+  tier: 0
+  family: operate
+
+prerequisites:
+  required: []
+
+execution:
+  spawns: [built-in]
+  context: fresh
+  reads:
+    - routing/god-deploy.yaml
+    - routing/god-observe.yaml
+    - routing/god-launch.yaml
+  writes: []
+
+dispatch:
+  deploy: /god-deploy
+  observe: /god-observe
+  launch: /god-launch
+
+success-path:
+  next-recommended: varies
+  outcome:
+    type: contextual
+    label: Ship dispatch route
+    reason: The next route depends on the requested shipping closure step.
+    allowed-next: [/god-deploy, /god-observe, /god-launch]
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: no direct state update; selected leaf command owns state
+  events: [agent.start, decision.route, agent.end]

package/routing/god-sync.yaml

@@ -8,7 +8,7 @@ metadata:
 
 prerequisites:
   required:
-    - check: file:.godpowers/PROGRESS.md
+    - check: state:initialized == true
       auto-complete: /god-init
       human-required: true
 

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

@@ -15,7 +15,7 @@ triggers:
     - "back after a week"
     - "coming back"
   state-conditions:
-    - "file:.godpowers/PROGRESS.md"
+    - "state:initialized == true"
 
 sequences:
   default:

package/schema/state.v1.json

@@ -269,7 +269,7 @@
       "properties": {
         "status": {
           "type": "string",
-          "enum": ["pending", "in-flight", "done", "skipped", "imported", "failed", "re-invoked"]
+          "enum": ["pending", "in-flight", "done", "skipped", "imported", "failed", "re-invoked", "not-required"]
         },
         "artifact": {
           "type": "string",
@@ -297,8 +297,75 @@
         "notes": {
           "type": "string",
           "description": "Free-form for skip reason, failure detail, etc."
+        },
+        "readiness-scope": {
+          "type": "string",
+          "description": "Deploy, observe, or launch readiness scope such as local-readiness, local-staging, ci-readiness, deployed-staging, live-target, or deferred-external-access."
+        },
+        "verified-target-type": {
+          "type": "string",
+          "description": "Target class verified by deploy, observe, or launch work, such as local-staging, ci, deployed-staging, production, or live."
+        },
+        "target-evidence": {
+          "type": "string",
+          "description": "Evidence source for a deploy, observe, or launch target, such as config, CI variable, IaC output, provider CLI output, docs, or current user input."
+        },
+        "external-access-deferral": {
+          "type": "string",
+          "description": "Relative artifact path or concise reason when deployed staging, provider, dashboard, or live launch access is deferred."
+        },
+        "waiting-artifact": {
+          "type": "string",
+          "description": "Relative artifact path for the smallest outstanding external access bundle."
+        },
+        "rollback-evidence": {
+          "type": "string",
+          "description": "Deploy rollback command, run result, or artifact path proving rollback was tested."
+        },
+        "slo-evidence": {
+          "type": "string",
+          "description": "Observability evidence for SLO definitions and error budget policy coverage."
+        },
+        "alert-evidence": {
+          "type": "string",
+          "description": "Observability evidence for alert definitions and alert response coverage."
+        },
+        "runbook-evidence": {
+          "type": "string",
+          "description": "Observability or launch evidence for tested runbooks."
+        },
+        "launch-evidence": {
+          "type": "string",
+          "description": "Launch evidence for live launch, local launch-readiness, source attribution, or launch deferral."
+        },
+        "verification": {
+          "type": "object",
+          "description": "Structured verification evidence used by executable gates instead of markdown STATE.md parsing.",
+          "properties": {
+            "commands": {
+              "type": "array",
+              "items": { "$ref": "#/$defs/VerificationCommand" }
+            }
+          },
+          "additionalProperties": true
         }
       }
+    },
+    "VerificationCommand": {
+      "type": "object",
+      "required": ["command", "status"],
+      "properties": {
+        "command": { "type": "string" },
+        "status": {
+          "type": "string",
+          "enum": ["pass", "passed", "green", "success", "succeeded", "ok", "fail", "failed", "red", "error", "skipped"]
+        },
+        "exitCode": { "type": "integer" },
+        "ranAt": { "type": "string", "format": "date-time" },
+        "durationMs": { "type": "integer", "minimum": 0 },
+        "diagnostics": { "type": "string" }
+      },
+      "additionalProperties": true
     }
   },
   "additionalProperties": false

package/skills/god-arch.md

@@ -27,7 +27,7 @@ After god-architect returns:
 1. Verify ARCH.md and ADRs exist on disk
 2. Spawn god-auditor to verify have-nots pass
 3. Run `npx godpowers gate --tier=arch --project=.` and do not proceed on a non-zero exit
-4. Update `.godpowers/PROGRESS.md`: Architecture status = done
+4. Run `npx godpowers state advance --step=arch --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md`.
 
 ## Pause Format
 

package/skills/god-build.md

@@ -61,7 +61,8 @@ For each slice in the wave (parallel):
    - If FAIL: return slice to god-executor with findings, including any
      overcomplication, speculative abstraction, or unrelated cleanup
    - If PASS: commit the slice atomically
-5. Update `.godpowers/build/STATE.md`
+5. Record build status and slice evidence in `.godpowers/state.json` so
+   `.godpowers/build/STATE.md` regenerates as a managed view.
 
 Move to next wave only when current wave is fully committed.
 
@@ -76,9 +77,10 @@ After all waves:
    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. Record the exact verification commands that passed in `.godpowers/build/STATE.md`
+5. Record the exact verification commands that passed in `.godpowers/state.json`
+   under `tiers.tier-2.build.verification.commands`
 6. Run `npx godpowers gate --tier=build --project=.` and do not proceed on a non-zero exit
-7. Update PROGRESS.md: Build status = done
+7. Run `npx godpowers state advance --step=build --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md` plus `.godpowers/build/STATE.md`.
 8. If the build plan or implementation establishes durable conventions, plan
    pillar updates through `lib/pillars.planArtifactSync`. Under
    `/god-mode --yolo`, apply those updates immediately and log the decision.
@@ -93,7 +95,7 @@ Pause for user ONLY if:
 ## On Completion
 
 ```
-Build complete: .godpowers/build/STATE.md
+Build complete: .godpowers/build/STATE.md (generated view)
 [N] slices delivered. [N] commits. All tests passing.
 
 Suggested next: /god-harden (adversarial review, gates Launch)

package/skills/god-capture.md

@@ -0,0 +1,45 @@
+---
+name: god-capture
+description: |
+  Capture verb dispatcher. Routes thoughts, todos, backlog items, and seeds
+  to the existing capture leaf commands.
+
+  Triggers on: "god capture", "/god-capture", "capture this", "note this",
+  "add todo", "add backlog", "plant seed"
+---
+
+# /god-capture
+
+Route capture intent to the smallest existing capture command.
+
+## Runtime module resolution
+
+Resolve the Godpowers runtime root before inspecting routes:
+
+1. If `<projectRoot>/routing/god-note.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 |
+|---|---|
+| `todo`, `task`, `remind`, `priority` | `/god-add-todo` |
+| `backlog`, `later`, `someday`, `future` | `/god-add-backlog` |
+| `when`, `if`, `after`, `once`, `trigger` | `/god-plant-seed` |
+| `note`, `thought`, `remember` | `/god-note` |
+
+Default to `/god-note` when no priority, backlog, or trigger 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 and the matched capture signal.
+4. Hand off to the selected leaf command after user confirmation.
+
+## Guardrails
+
+- Do not write notes, todos, backlog items, or seeds directly from this dispatcher.
+- Do not assign priority unless the user provided priority evidence.
+- Keep each capture leaf callable as a direct shortcut.

package/skills/god-deploy.md

@@ -13,15 +13,15 @@ Spawn the **god-deploy-engineer** agent in a fresh context via the host platform
 
 ## Setup
 
-1. Verify build is complete (`.godpowers/build/STATE.md` exists with passing state).
+1. Verify build is complete through `.godpowers/state.json` `tier-2.build.status == done` and passing build verification commands.
 2. Verify all tests pass.
 3. Spawn god-deploy-engineer with ARCH and stack DECISION paths.
-4. The agent writes `.godpowers/deploy/STATE.md`.
+4. The agent returns structured deploy evidence for `.godpowers/state.json`; the generated `.godpowers/deploy/STATE.md` view refreshes after state mutation.
 
 ## Verification
 
 After god-deploy-engineer returns:
-1. Verify STATE.md exists on disk
+1. Verify deploy evidence is recorded in `.godpowers/state.json`
 2. Verify rollback procedure has been tested (not paper-only)
 3. Verify the deploy path is one of:
    - real staging or production target tested
@@ -29,15 +29,17 @@ After god-deploy-engineer returns:
      commands
    - local/CI deploy readiness complete with deployed staging verification
      deferred in `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md`
-4. Update `.godpowers/PROGRESS.md`: Deploy status can be done when a tested
-   real target or tested local staging harness exists. If deployed staging is
-   deferred, annotate Deploy as done-local with the waiting artifact path and
-   do not pause unless the user explicitly requested staging.
+4. Run `npx godpowers state advance --step=deploy --status=done --project=.`
+   only when a tested real target or tested local staging harness exists. If
+   deployed staging is deferred, record the waiting artifact path in
+   `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` and keep that evidence
+   in `state.json` through the owning deploy command rather than editing the
+   generated progress or deploy state views.
 
 ## On Completion
 
 ```
-Deploy pipeline complete: .godpowers/deploy/STATE.md
+Deploy pipeline complete: .godpowers/deploy/STATE.md (generated view)
 
 Suggested next: /god-observe (wire SLOs, alerts, runbooks)
 ```
@@ -69,15 +71,15 @@ known, do not use it as staging without explicit user approval.
 
 ## Re-invocation contract
 
-What happens if `/god-deploy` is run when `.godpowers/deploy/STATE.md` already exists:
+What happens if `/god-deploy` is run when deploy state evidence already exists:
 
 | Existing state | Behavior |
 |---|---|
-| File does not exist | Spawn god-deploy-engineer; produce file; mark sub-step done |
-| File exists, passes lint, state.json says `done` | Pause: ask user (A) re-run anyway with diff preview, (B) treat as imported (no-op), (C) cancel |
-| File exists, fails lint or have-nots | Spawn god-deploy-engineer in update mode with current file + findings as input. Diff preview before overwrite. |
-| File exists, state.json says `pending` | Treat as imported: hash + register, no agent spawn. User can `/god-deploy --force` to re-run. |
-| `--force` flag passed | Snapshot existing file to `.godpowers/.trash/god-deploy-<ts>/`. Spawn agent fresh. |
+| State evidence does not exist | Spawn god-deploy-engineer; record deploy evidence; mark sub-step done |
+| State evidence exists and state.json says `done` | Pause: ask user (A) re-run anyway with diff preview, (B) treat as imported (no-op), (C) cancel |
+| State evidence fails checks or the owning wrapper reports a generated view checksum warning | Spawn god-deploy-engineer in update mode with current evidence plus findings as input. Diff preview before overwrite. |
+| State evidence exists, state.json says `pending` | Treat as imported: hash + register, no agent spawn. User can `/god-deploy --force` to re-run. |
+| `--force` flag passed | Snapshot existing evidence to `.godpowers/.trash/god-deploy-<ts>/`. Spawn agent fresh. |
 | `--dry-run` flag passed | Show what would happen; touch nothing |
 
 Snapshots in `.trash/` are recoverable via `/god-restore` for 30 days.

package/skills/god-design.md

@@ -96,9 +96,9 @@ applied to design.
 
 After god-designer and god-design-reviewer return:
 1. Verify `DESIGN.md` exists on disk
-2. Verify `.godpowers/design/STATE.md` exists on disk
+2. Record design lint, review verdict, and command history in `.godpowers/state.json`
 3. Run `npx godpowers gate --tier=design --project=.` and do not proceed on a non-zero exit
-4. Update `.godpowers/PROGRESS.md`: Design status = done when the project requires design
+4. Run `npx godpowers state advance --step=design --status=done --project=.` when the project requires design, or `npx godpowers state advance --step=design --status=not-required --project=.` when design is explicitly not required.
 
 ## Output
 
@@ -107,7 +107,7 @@ Project root:
 - `PRODUCT.md` (impeccable strategic file, when impeccable installed)
 
 Inside `.godpowers/design/`:
-- `STATE.md` (lint history, version, impeccable command log)
+- `STATE.md` (generated design state view from `.godpowers/state.json`)
 - `HISTORY.md` (append-only log of design changes; populated by god-designer)
 - `REJECTED.md` (append-only log of blocked changes; populated by god-design-reviewer)
 

package/skills/god-doctor.md

@@ -48,7 +48,7 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 112 skills installed
+  [OK] 117 skills installed
   [OK] 40 agents installed
   [OK] VERSION matches (2.3.1)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now

package/skills/god-extend.md

@@ -0,0 +1,48 @@
+---
+name: god-extend
+description: |
+  Extend verb dispatcher. Routes extension installation, inspection, removal,
+  testing, and authoring intent to existing extension leaf commands.
+
+  Triggers on: "god extend", "/god-extend", "install extension",
+  "list extensions", "remove extension", "scaffold extension"
+---
+
+# /god-extend
+
+Route extension intent to the smallest existing extension command.
+
+## Runtime module resolution
+
+Resolve the Godpowers runtime root before inspecting routes:
+
+1. If `<projectRoot>/routing/god-extension-add.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 |
+|---|---|
+| `scaffold`, `author`, `create pack` | `/god-extension-scaffold` |
+| `add`, `install` | `/god-extension-add` |
+| `list`, `installed` | `/god-extension-list` |
+| `info`, `inspect`, `details` | `/god-extension-info` |
+| `remove`, `uninstall` | `/god-extension-remove` |
+| `test`, `verify` | `/god-test-extension` |
+| `agent`, `custom agent` | `/god-build-agent` |
+
+Default to `/god-extension-list` 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 whether the target mutates installed packs.
+4. Hand off to the selected leaf command after user confirmation.
+
+## Guardrails
+
+- Do not install, remove, scaffold, or test extension packs directly from this dispatcher.
+- Do not bypass package legitimacy checks from extension leaf commands.
+- Keep each extension leaf callable as a direct shortcut.

package/skills/god-fast.md

@@ -3,7 +3,7 @@ name: god-fast
 description: |
   Make a quick inline edit without full Godpowers planning overhead. For trivial
   changes: typo fixes, config tweaks, single-line updates. No agents, no plans,
-  no PROGRESS.md updates.
+  no state mutation.
 
   Triggers on: "god fast", "/god-fast", "quick fix", "trivial change", "tiny tweak"
 ---
@@ -36,7 +36,7 @@ Skip the full pipeline. Make a small edit inline.
 
 - If running tests reveals regressions: STOP. Switch to /god-build or /god-debug.
 - If the change touches more than 3 lines: STOP. Switch to /god-build.
-- Skip PROGRESS.md updates (this is below the planning threshold).
+- Skip state mutation and generated progress view refreshes because this is below the planning threshold.
 
 ## On Completion
 

package/skills/god-feature.md

@@ -57,7 +57,7 @@ Spawn **god-planner** scoped to the feature only.
 Then run god-executor + god-spec-reviewer + god-quality-reviewer per slice.
 
 ### Phase 4: Deploy
-Use existing deploy pipeline (.godpowers/deploy/STATE.md). No new pipeline.
+Use existing deploy pipeline from `.godpowers/state.json` deploy evidence. No new pipeline.
 Feature flag the rollout if the feature is high-risk.
 
 ### Phase 5: Harden (just the new code)