godpowers 2.6.0 → 3.0.0

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,22 +21,26 @@ 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
 
-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.
-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.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/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

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: