godpowers 2.6.0 → 2.7.0

package/skills/god-resume-work.md

@@ -2,8 +2,9 @@
 name: god-resume-work
 description: |
   Resume work from a previous session. Reads .godpowers/HANDOFF.md if it
-  exists, otherwise re-derives state from PROGRESS.md and disk. Continues
-  from the last incomplete sub-step.
+  exists, otherwise re-derives state from state.json and disk, with
+  PROGRESS.md as a generated legacy fallback. Continues from the last
+  incomplete sub-step.
 
   Triggers on: "god resume", "/god-resume-work", "resume work", "continue",
   "pick up where I left off"
@@ -24,9 +25,9 @@ Load context and continue.
    - Confirm with user: "Pick up here?"
    - If yes: route to the specific next action
 
-3. If only PROGRESS.md exists:
+3. If only generated legacy PROGRESS.md exists:
    - Run the same logic as /god-next
-   - Suggest the next command based on state
+   - Suggest the next command based on re-derived state
 
 4. After resuming, archive HANDOFF.md:
    - Move to `.godpowers/archive/HANDOFF-[timestamp].md` so the trail is preserved

package/skills/god-roadmap-update.md

@@ -43,7 +43,7 @@ Agent updates the roadmap and re-validates have-nots.
 After god-roadmap-updater returns:
 1. Verify ROADMAP.md still passes have-nots (R-01 through R-07)
 2. Verify Roadmap Changelog section is appended
-3. Update PROGRESS.md if applicable
+3. If the update changes tracked roadmap completion, run `npx godpowers state advance --step=roadmap --status=done --project=.` or the owning command wrapper.
 
 ## On Completion
 

package/skills/god-roadmap.md

@@ -24,7 +24,7 @@ After god-roadmapper returns:
 1. Verify ROADMAP.md exists on disk
 2. Spawn god-auditor to verify have-nots pass
 3. Run `npx godpowers gate --tier=roadmap --project=.` and do not proceed on a non-zero exit
-4. Update `.godpowers/PROGRESS.md`: Roadmap status = done
+4. Run `npx godpowers state advance --step=roadmap --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md`.
 
 ## On Completion
 

package/skills/god-rollback.md

@@ -38,7 +38,7 @@ Examples:
 5. Mark each tier `status: pending` in state.json.
 6. Append a `op:rollback` event to the reflog with the full closure.
 7. Truncate the linkage map entries belonging to rolled-back artifacts.
-8. Update PROGRESS.md.
+8. Regenerate managed state views from `state.json`.
 
 ## Difference from /god-undo
 

package/skills/god-skip.md

@@ -32,7 +32,7 @@ The reason is required. Skips without reason are rejected.
    mandatory; e.g. /god-mode rejects skipping the final /god-sync).
 3. Mark the sub-step `status: skipped` in state.json with `skipped-reason`.
 4. Append a `op:skip` event to the reflog.
-5. Update PROGRESS.md so the user sees the skip annotated.
+5. Regenerate the managed progress view from `state.json` so the user sees the skip annotated.
 
 ## What skip does NOT do
 
@@ -59,7 +59,7 @@ Reverse a previous skip. Marks the sub-step `pending` again.
 
 ## Implementation
 
-Built-in. Reads + writes `state.json` and PROGRESS.md. Appends to reflog.
+Built-in. Reads and writes `state.json`, regenerates the managed progress view, and appends to reflog.
 
 
 ## Locking

package/skills/god-stack.md

@@ -22,7 +22,7 @@ Spawn the **god-stack-selector** agent in a fresh context via the host platform'
 After god-stack-selector returns:
 1. Verify DECISION.md exists on disk
 2. Run `npx godpowers gate --tier=stack --project=.` and do not proceed on a non-zero exit
-3. Update `.godpowers/PROGRESS.md`: Stack status = done
+3. Run `npx godpowers state advance --step=stack --status=done --project=.` to update `state.json` and regenerate `.godpowers/PROGRESS.md`.
 
 ## On Completion
 

package/skills/god-standards.md

@@ -22,7 +22,7 @@ Run quality gate check on an artifact.
 
 ## Process
 
-1. Identify the artifact to check (user provides, or auto-detect from PROGRESS.md)
+1. Identify the artifact to check, using the user-provided path first, then `state.json`, then generated progress view fallback.
 2. Resolve the Godpowers runtime root: use `<projectRoot>` when `<projectRoot>/lib/router.js` exists, otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`
 3. Look up the routing for the relevant tier (`<runtimeRoot>/lib/router.js` getStandards)
 4. Spawn god-standards-check in fresh context with:

package/skills/god-status.md

@@ -28,11 +28,11 @@ proactive checks, blockers, planning visibility, and the next action first.
 
 ## Process
 
-1. Check whether `.godpowers/PROGRESS.md` or `.godpowers/state.json` exists. If neither exists, report that no Godpowers project was found and suggest `/god-init`.
+1. Check whether `.godpowers/state.json` exists. If it does not, treat `.godpowers/PROGRESS.md` only as a generated legacy fallback; if neither exists, report that no Godpowers project was found and suggest `/god-init`.
 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 PROGRESS.md only as fallback or legacy explanation when state.json is missing.
+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.

package/skills/god-story.md

@@ -23,7 +23,7 @@ Add a new story under `.godpowers/stories/<feature-slug>/`.
 
 ## Process
 
-1. Verify `.godpowers/PROGRESS.md` exists. If not: `/god-init` first.
+1. Verify `.godpowers/state.json` exists. If not: `/god-init` first.
 2. Spawn `god-storyteller` agent in fresh context.
 3. Storyteller reads PRD/ARCH for context, validates user-story format,
    writes the file.

package/skills/god-sync.md

@@ -110,8 +110,8 @@ Updated:
   - prd/PRD.md (added requirement P-MUST-12)
   - arch/ARCH.md (added ADR-007)
   - roadmap/ROADMAP.md (Milestone 2 marked complete)
-  - deploy/STATE.md (new env var)
-  - observe/STATE.md (new SLO)
+  - state.json tier-3.deploy (new env var)
+  - state.json tier-3.observe (new SLO)
   - backlog/BACKLOG.md (entry resolved)
   - todos/TODOS.md (1 todo marked done)
   - threads/auth-migration.md (progress note)

package/workflows/bluefield-arc.yaml

@@ -56,10 +56,8 @@ jobs:
         - .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/launch/STATE.md
+        - .godpowers/state.json
+        - .godpowers/build/PLAN.md
         - .godpowers/harden/FINDINGS.md
 
   prd:

package/workflows/brownfield-arc.yaml

@@ -72,10 +72,8 @@ jobs:
         - .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/launch/STATE.md
+        - .godpowers/state.json
+        - .godpowers/build/PLAN.md
         - .godpowers/harden/FINDINGS.md
 
   steady-state-handoff: