godpowers 2.6.0 → 2.7.0

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-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-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-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)

package/skills/god-harden.md

@@ -13,7 +13,7 @@ Spawn the **god-harden-auditor** agent in a fresh context via the host platform'
 
 ## Setup
 
-1. Verify build is complete (`.godpowers/build/STATE.md` exists).
+1. Verify build is complete through `.godpowers/state.json` `tier-2.build.status == done`.
 2. Spawn god-harden-auditor with full code access.
 3. The agent writes `.godpowers/harden/FINDINGS.md`.
 
@@ -23,8 +23,8 @@ After god-harden-auditor returns:
 1. Verify FINDINGS.md exists on disk
 2. Run `npx godpowers gate --tier=harden --project=.` and do not proceed on a non-zero exit
 3. Read findings classification:
-   - If any Critical: PROGRESS.md status = failed, launch is BLOCKED
-   - If only High/Medium/Low: PROGRESS.md status = done
+   - If any Critical: run `npx godpowers state advance --step=harden --status=failed --project=.` and keep launch BLOCKED
+   - If only High/Medium/Low: run `npx godpowers state advance --step=harden --status=done --project=.`
 
 ## Have-Nots
 

package/skills/god-hotfix.md

@@ -72,7 +72,7 @@ Spawn **god-observability-engineer** briefly:
 - Confirm recovery in metrics
 
 ### Phase 7: Schedule Postmortem
-Update PROGRESS.md with a TODO:
+Record a state-backed follow-up TODO through the owning command wrapper:
 "Run /god-postmortem within 48 hours for incident <id>"
 
 Hotfix doesn't replace postmortem; it precedes it.

package/skills/god-init.md

@@ -3,7 +3,8 @@ name: god-init
 description: |
   Initialize a Godpowers project. Detects operating mode (greenfield, gap-fill,
   audit, multi-repo) and project scale. Creates native Pillars project context
-  plus the .godpowers/ workflow state directory with PROGRESS.md.
+  plus the .godpowers/ workflow state directory with state.json and generated
+  PROGRESS.md.
 
   Triggers on: "god init", "start a project", "new project", "initialize"
 ---
@@ -18,9 +19,11 @@ This skill is a thin wrapper. Detection happens automatically; user never
 needs to specify a mode.
 
 1. Check if `.godpowers/` already exists:
-   - If yes: read PROGRESS.md, call `lib/pillars.pillarizeExisting(projectRoot)`
-     to ensure the existing Godpowers project is also Pillar-ized, report
-     current state, ask if user wants to reset or resume
+   - If yes: read `.godpowers/state.json`, use generated `.godpowers/PROGRESS.md`
+     only as a legacy fallback, call
+     `lib/pillars.pillarizeExisting(projectRoot)` to ensure the existing
+     Godpowers project is also Pillar-ized, report current state, ask if user
+     wants to reset or resume
    - If no: proceed with initialization
 
 2. **Auto-detect what kind of project this is** (background, no user prompt):
@@ -124,7 +127,8 @@ needs to specify a mode.
    - For brownfield: schedule preflight before archaeology + reconstruction
    - For bluefield: load org-context, then schedule preflight as constraint intake
    - Create directory structure
-   - Write PROGRESS.md with mode, scale, timestamp, tier states
+   - Write `.godpowers/state.json` with mode, scale, timestamp, tier states,
+     then regenerate the managed `.godpowers/PROGRESS.md` view
    - Return mode/scale/announcement to this skill
 
 8. Detect scale by analyzing the description:
@@ -150,7 +154,7 @@ needs to specify a mode.
      deploy.md
      observe.md
    .godpowers/
-     PROGRESS.md
+     PROGRESS.md              # generated managed view
      prep/
        INITIAL-FINDINGS.md
        IMPORTED-CONTEXT.md   # only when legacy planning / Superpowers / BMAD context exists
@@ -167,7 +171,7 @@ needs to specify a mode.
      harden/
    ```
 
-10. Write PROGRESS.md with mode, scale, timestamp, all tiers set to `pending`
+10. Write `state.json` with mode, scale, timestamp, and all tiers set to `pending`, then regenerate `.godpowers/PROGRESS.md`
 
 11. Report to the user:
    - Detected mode and scale
@@ -186,7 +190,7 @@ needs to specify a mode.
 
 ## Output
 
-`.godpowers/PROGRESS.md` created with initial state.
+`.godpowers/state.json` created with initial state and `.godpowers/PROGRESS.md` generated as a managed human view.
 
 Always create `.godpowers/prep/INITIAL-FINDINGS.md`. This is Godpowers'
 durable answer to "what did init find in this codebase?" It captures codebase
@@ -201,7 +205,7 @@ as hypothesis-level input only.
 
 ## Native Pillars context and AI-tool context
 
-After PROGRESS.md is written, Pillars context is already present. Every
+After `state.json` is written and the progress view is generated, Pillars context is already present. Every
 Godpowers project uses `AGENTS.md` plus `agents/*.md` as its native project
 truth layer.
 
@@ -243,7 +247,7 @@ If the user later wants to enable it manually, they run `/god-context on`.
 
 ## Mode D detection (multi-repo workspace)
 
-After PROGRESS.md is written, also check whether this directory is
+After `state.json` is written, also check whether this directory is
 part of a multi-repo suite:
 
 1. Call `lib/multi-repo-detector.detect(projectRoot)`.

package/skills/god-launch.md

@@ -17,21 +17,23 @@ Spawn the **god-launch-strategist** agent in a fresh context via the host platfo
 2. If Critical findings exist: REFUSE to proceed. Tell user to resolve or
    explicitly accept the risk first.
 3. Spawn god-launch-strategist with PRD path and harden FINDINGS.md path.
-4. The agent writes `.godpowers/launch/STATE.md` plus landing copy artifacts.
+4. The agent returns structured launch evidence for `.godpowers/state.json` plus landing copy artifacts; the generated `.godpowers/launch/STATE.md` view refreshes after state mutation.
 
 ## Verification
 
 After god-launch-strategist returns:
-1. Verify STATE.md exists on disk
+1. Verify launch evidence is recorded in `.godpowers/state.json`
 2. Verify landing copy passes substitution test
 3. Verify OG cards rendered (not just meta tags)
 4. Verify one of:
    - launch target is live and smoke checked
    - local launch-readiness harness passed and external access bundle is the
      only missing item
-5. Update `.godpowers/PROGRESS.md`: Launch status = done only when live launch
-   or explicit local launch-readiness scope is complete. If external access is
-   missing, mark Launch = waiting-for-external-access.
+5. Run `npx godpowers state advance --step=launch --status=done --project=.`
+   only when live launch or explicit local launch-readiness scope is complete.
+   If external access is missing, record the waiting artifact path in launch
+   state through the owning command wrapper rather than editing the generated
+   progress or launch state views.
 
 ## Pause Conditions
 
@@ -41,7 +43,7 @@ approval require human input.
 ## On Completion
 
 ```
-Launch complete: .godpowers/launch/STATE.md
+Launch complete: .godpowers/launch/STATE.md (generated view)
 
 All Godpowers tiers done. Project is live.
 
@@ -71,15 +73,15 @@ approval.
 
 ## Re-invocation contract
 
-What happens if `/god-launch` is run when `.godpowers/launch/STATE.md` already exists:
+What happens if `/god-launch` is run when launch state evidence already exists:
 
 | Existing state | Behavior |
 |---|---|
-| File does not exist | Spawn god-launch-strategist; 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-launch-strategist 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-launch --force` to re-run. |
-| `--force` flag passed | Snapshot existing file to `.godpowers/.trash/god-launch-<ts>/`. Spawn agent fresh. |
+| State evidence does not exist | Spawn god-launch-strategist; record launch 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-launch-strategist 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-launch --force` to re-run. |
+| `--force` flag passed | Snapshot existing evidence to `.godpowers/.trash/god-launch-<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-lifecycle.md

@@ -17,7 +17,8 @@ Show project phase and contextually appropriate workflows.
 
 1. Detect lifecycle phase from disk:
    - **No `.godpowers/`** -> Pre-init
-   - **`.godpowers/PROGRESS.md` exists, not all tiers done** -> In progress
+   - **`.godpowers/state.json` exists, not all tracked steps done** -> In progress
+   - **Only generated legacy `.godpowers/PROGRESS.md` exists** -> In progress after re-deriving state from disk
    - **All tiers done, no special markers** -> Steady state
    - **`.godpowers/postmortems/<id>/` exists with no POSTMORTEM.md** -> Post-incident pending
    - **`.godpowers/migrations/<slug>/MIGRATION.md` exists, status != complete** -> In-migration

package/skills/god-mode.md

@@ -19,8 +19,9 @@ workflow.
 
 1. Resolve whether this is a new project run or a resume:
    - If `.godpowers/state.json`, `.godpowers/PROGRESS.md`, or
-     `.godpowers/CHECKPOINT.md` exists, this is a resume. Do not ask the user
-     to describe the project again. Call
+     `.godpowers/CHECKPOINT.md` exists, this is a resume. Treat `state.json`
+     as the source of truth and `PROGRESS.md` as a generated legacy fallback.
+     Do not ask the user to describe the project again. Call
      `lib/pillars.pillarizeExisting(projectRoot)` first, then rehydrate intent
      from disk and continue.
    - If no durable Godpowers state exists and no project description was
@@ -41,7 +42,7 @@ workflow.
      starting with `agents/context.md` and `agents/repo.md`
    - `.godpowers/CHECKPOINT.md` first, when present
    - `.godpowers/state.json`
-   - `.godpowers/PROGRESS.md`
+   - `.godpowers/PROGRESS.md` only as a generated legacy fallback when state is missing
    - `.godpowers/intent.yaml`, when present
    - `.godpowers/prep/INITIAL-FINDINGS.md`, when present
    - `.godpowers/prep/IMPORTED-CONTEXT.md`, when present
@@ -78,7 +79,7 @@ workflow.
      - The detected mode (A/B/C/E)
      - The active flags
      - Instruction that existing `.godpowers` state means resume, not prompt
-     - Instruction to read `.godpowers/PROGRESS.md` from disk if it exists
+     - Instruction to read `.godpowers/state.json` from disk, using `.godpowers/PROGRESS.md` only as generated legacy fallback when state is missing
      - Instruction to read `.godpowers/prep/INITIAL-FINDINGS.md` and
        `.godpowers/prep/IMPORTED-CONTEXT.md` if present before choosing the
        first planning or build step

package/skills/god-observe.md

@@ -13,14 +13,14 @@ Spawn the **god-observability-engineer** agent in a fresh context via the host p
 
 ## Setup
 
-1. Verify `.godpowers/deploy/STATE.md` exists. App is deployed.
+1. Verify `.godpowers/state.json` records `tier-3.deploy.status == done`.
 2. Spawn god-observability-engineer with PRD (for success metrics) and ARCH paths.
-3. The agent writes `.godpowers/observe/STATE.md`.
+3. The agent returns structured observability evidence for `.godpowers/state.json`; the generated `.godpowers/observe/STATE.md` view refreshes after state mutation.
 
 ## Verification
 
 After god-observability-engineer returns:
-1. Verify STATE.md exists on disk
+1. Verify observability evidence is recorded in `.godpowers/state.json`
 2. Verify each SLO has an error budget policy
 3. Verify each alert has a runbook
 4. Verify provider work is one of:
@@ -28,14 +28,16 @@ After god-observability-engineer returns:
    - provider-neutral definitions as code created and locally checked
    - missing dashboard/API credentials appended to the single external access
      bundle
-5. Update `.godpowers/PROGRESS.md`: Observe status = done only for verified
-   real provider config or local definitions as code. If external access is
-   missing, mark Observe = waiting-for-external-access.
+5. Run `npx godpowers state advance --step=observe --status=done --project=.`
+   only for verified real provider config or local definitions as code. If
+   external access is missing, record the missing access bundle in deploy or
+   observe state through the owning command wrapper rather than editing the
+   generated progress or observe state views.
 
 ## On Completion
 
 ```
-Observability complete: .godpowers/observe/STATE.md
+Observability complete: .godpowers/observe/STATE.md (generated view)
 
 Suggested next: /god-harden (adversarial security review, gates Launch)
 ```
@@ -53,15 +55,15 @@ named command cannot run without one exact credential.
 
 ## Re-invocation contract
 
-What happens if `/god-observe` is run when `.godpowers/observe/STATE.md` already exists:
+What happens if `/god-observe` is run when observe state evidence already exists:
 
 | Existing state | Behavior |
 |---|---|
-| File does not exist | Spawn god-observability-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-observability-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-observe --force` to re-run. |
-| `--force` flag passed | Snapshot existing file to `.godpowers/.trash/god-observe-<ts>/`. Spawn agent fresh. |
+| State evidence does not exist | Spawn god-observability-engineer; record observability 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-observability-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-observe --force` to re-run. |
+| `--force` flag passed | Snapshot existing evidence to `.godpowers/.trash/god-observe-<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-pause-work.md

@@ -15,7 +15,7 @@ Create a context handoff so you can resume cleanly later.
 
 ## Process
 
-1. Read `.godpowers/PROGRESS.md` to capture current state
+1. Read `.godpowers/state.json` to capture current state; use `.godpowers/PROGRESS.md` only as a generated legacy fallback when state is missing.
 2. Identify what was actively being worked on:
    - Which slice? Which agent was running?
    - What was the next step?
@@ -53,7 +53,7 @@ Paused: [timestamp]
 `/god-resume-work` to load this context, then continue.
 ```
 
-5. Update PROGRESS.md to mark current sub-step as `in-flight` if not already
+5. Run `npx godpowers state advance --step=<current-step> --status=in-flight --project=.` if the current sub-step is not already in flight.
 
 ## On Completion
 

package/skills/god-prd.md

@@ -13,11 +13,12 @@ Spawn the **god-pm** agent in a fresh context via the host platform's native age
 
 ## Setup
 
-1. If `.godpowers/PROGRESS.md` does not exist: tell the user to run `/god-init` first
+1. If `.godpowers/state.json` does not exist: tell the user to run `/god-init` first.
 2. Read `.godpowers/prep/INITIAL-FINDINGS.md` if present.
 3. Read `.godpowers/prep/IMPORTED-CONTEXT.md` if present.
-4. Spawn god-pm with the user's project description from PROGRESS.md plus any
-   prep artifacts. Prep artifacts are context, not source of truth.
+4. Spawn god-pm with the user's project description from `state.json`,
+   `.godpowers/intent.yaml`, and any prep artifacts. Prep artifacts are
+   context, not source of truth.
 5. The agent writes `.godpowers/prd/PRD.md`
 6. The agent runs have-nots checks before declaring done
 7. If god-pm pauses for a human question: relay to user using pause format
@@ -31,7 +32,7 @@ After god-pm returns:
 1. Verify `.godpowers/prd/PRD.md` exists on disk
 2. Spawn god-auditor briefly to verify have-nots pass
 3. Run `npx godpowers gate --tier=prd --project=.` and do not proceed on a non-zero exit
-4. Update `.godpowers/PROGRESS.md`: PRD status = done
+4. Run `npx godpowers state advance --step=prd --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md`.
 
 ## Pause Format
 

package/skills/god-quick.md

@@ -39,7 +39,7 @@ workflow.
 
 - Planning tier (PRD/ARCH/ROADMAP/STACK)
 - Build planning into waves (single slice only)
-- PROGRESS.md updates if no `.godpowers/` exists
+- State mutation if no `.godpowers/` exists
 
 ## On Completion
 

package/skills/god-repo.md

@@ -23,7 +23,7 @@ After god-repo-scaffolder returns:
 1. Verify AUDIT.md exists on disk
 2. Verify CI passes on the empty scaffold
 3. Run `npx godpowers gate --tier=repo --project=.` and do not proceed on a non-zero exit
-4. Update `.godpowers/PROGRESS.md`: Repo status = done
+4. Run `npx godpowers state advance --step=repo --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md`.
 
 ## On Completion