godpowers 1.6.11 → 1.6.13

package/skills/god-next.md

@@ -22,6 +22,9 @@ Before reading routing data or calling runtime modules, resolve the Godpowers ru
 1. If `<projectRoot>/lib/router.js` exists, use the repository checkout runtime at `<projectRoot>`.
 2. Otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`, where `<tool-config-dir>` is the directory that contains this installed skill, such as `~/.claude`, `~/.codex`, `~/.cursor`, `~/.windsurf`, or `~/.gemini`.
 3. Read routing definitions from `<runtimeRoot>/routing/*.yaml` and recipes from `<runtimeRoot>/routing/recipes/*.yaml`.
+4. For status output, load `<runtimeRoot>/lib/dashboard.js` and call
+   `dashboard.compute(projectRoot)`. Use `dashboard.render(result)` for the
+   shared dashboard section before adding route-specific detail.
 
 ## Three modes of invocation
 
@@ -333,11 +336,31 @@ recommending archaeology, reconstruction, project-run readiness, pillars, or ref
 
 ## Output Format
 
-```
+`/god-next` must emit the same Godpowers Dashboard shape used by
+`/god-status`, then add routing detail and the proposition block.
+Prefer the executable `lib/dashboard.js` output over manually recomputing the
+same fields. If the module is unavailable, say
+`Dashboard engine: unavailable, manual scan used`.
+
+```text
 Godpowers Next
 
-Current state: [where we are]
-Progress: [pct]% ([done] of [total] steps complete; current step [n] of [total])
+Godpowers Dashboard
+
+Current status:
+  State: proposal
+  Phase: [plain-language phase] (tier [human ordinal] of [human total])
+  Step: [current step label] (step [n] of [total steps])
+  Progress: [pct]% ([done] of [total] steps complete)
+  Worktree: [clean | modified files unstaged | staged changes | mixed]
+  Index: [untouched | staged files listed]
+
+Planning visibility:
+  PRD: [done | pending | missing | deferred] [path when present]
+  Roadmap: [done | pending | missing | deferred] [path when present]
+  Current milestone: [roadmap milestone, phase, tier, or next planning gate]
+  Completion: [pct]% [basis from state.json, PROGRESS.md, or artifacts]
+
 Suggested next: [/god-X]
 
 Why: [one-line reason]
@@ -359,14 +382,21 @@ Previous tier had standards failures. Address before proceeding:
 Suggested: /god-redo [tier] OR /god-skip [tier] --reason="..."
 
 Proactive checks:
-  Checkpoint: [fresh | refreshed | stale]
-  Reviews: [none | N pending]
-  Sync: [fresh | suggested | local helper ran]
-  Docs: [fresh | suggested]
-  Runtime: [not-applicable | suggested | ran]
-  Security: [clear | suggested]
-  Dependencies: [clear | suggested]
-  Hygiene: [fresh | suggested]
+  Checkpoint: [fresh | refreshed | missing | stale]
+  Reviews: [none | N pending, suggest /god-review-changes]
+  Sync: [fresh | missing | stale | local helper ran | suggest /god-sync]
+  Docs: [fresh | possible drift, suggest /god-docs]
+  Runtime: [not-applicable | known URL, suggest /god-test-runtime | no known URL, defer deployed verification]
+  Security: [clear | sensitive files changed, suggest /god-harden]
+  Dependencies: [clear | dependency files changed, suggest /god-update-deps]
+  Hygiene: [fresh | stale, suggest /god-hygiene]
+
+Open items:
+  1. [missing prerequisite, blocker, pending review, or none]
+
+Next:
+  Recommended: [/god-X or exact user decision]
+  Why: [one sentence tied to disk state]
 ```
 
 ## Proposition Closeout

package/skills/god-status.md

@@ -15,8 +15,12 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
 
 1. Check if `.godpowers/PROGRESS.md` exists
    - If not: "No Godpowers project found. Run `god init` to start."
-2. Read PROGRESS.md for recorded state
-3. Scan ALL artifact paths on disk:
+2. Resolve the runtime root and load `<runtimeRoot>/lib/dashboard.js`.
+3. Call `dashboard.compute(projectRoot)` and use the returned object as the
+   primary dashboard source.
+4. Read PROGRESS.md for recorded state when state.json is missing or when you
+   need to explain legacy progress.
+5. Scan ALL artifact paths on disk:
    - `.godpowers/prd/PRD.md`
    - `.godpowers/arch/ARCH.md`
    - `.godpowers/roadmap/ROADMAP.md`
@@ -29,12 +33,13 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - `.godpowers/harden/FINDINGS.md`
    - `.godpowers/SYNC-LOG.md`
    - `.godpowers/CHECKPOINT.md`
-4. For each artifact found: run a lightweight have-nots check
-5. Compare disk state to PROGRESS.md state:
+6. For each artifact found: run a lightweight have-nots check
+7. Compare disk state to PROGRESS.md state:
    - If PROGRESS.md says "done" but artifact is missing: FLAG as phantom resume
    - If artifact exists but PROGRESS.md says "pending": FLAG as untracked work
-6. Report:
+8. Report the Godpowers Dashboard from `dashboard.render(result)`:
    - Current mode and scale
+   - Current phase, tier number, step label, and step number
    - Progress summary: percentage, completed step count, current step number
    - Planning visibility: PRD status, roadmap status, active milestone, and
      completion basis
@@ -45,17 +50,26 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - Per-tier status (with disk verification)
    - Any inconsistencies between PROGRESS.md and disk
    - Suggested next action
-7. If inconsistencies found: offer to repair PROGRESS.md to match disk truth
+9. If inconsistencies found: offer to repair PROGRESS.md to match disk truth
+
+If the runtime module is unavailable, fall back to the manual scan below and
+say `Dashboard engine: unavailable, manual scan used`.
 
 ## Output Format
 
-```
-Godpowers Status
+```text
+Godpowers Dashboard
 
 Mode: A (greenfield)    Scale: medium
 Started: 2026-05-09
-Progress: 15% (2 of 13 steps complete; current step 3 of 13)
-Current: Tier 1 Planning / Architecture
+
+Current status:
+  State: in progress
+  Phase: Planning (tier 2 of 4, internal tier-1)
+  Step: Architecture (step 3 of 13)
+  Progress: 15% (2 of 13 steps complete)
+  Worktree: clean
+  Index: untouched
 
 Planning visibility:
   PRD: done .godpowers/prd/PRD.md
@@ -83,6 +97,7 @@ Proactive opportunities:
   Sync: fresh
   Docs: possible drift, suggest /god-docs
   Runtime: known local URL, suggest /god-test-runtime
+  Automation: available via codex-app, suggest /god-automation-setup
   Security: clear
   Dependencies: clear
   Hygiene: stale, suggest /god-hygiene
@@ -121,7 +136,12 @@ Suite (Mode D) status:
   This repo is a sibling of suite "my-products" (hub: ../hub)
   Run /god-suite-status to see all 3 repos and meta-linter findings.
 
-Next: god roadmap
+Open items:
+  1. Roadmap and stack are still pending
+
+Next:
+  Recommended: /god-roadmap
+  Why: architecture is done and the roadmap is the next planning gate.
 ```
 
 ## Proposition Closeout
@@ -155,6 +175,8 @@ Report:
   `docs drift-check already logged`
 - Runtime: `not-applicable`, `known URL, suggest /god-test-runtime`, or
   `no known URL, defer deployed verification`
+- Automation: `not configured`, `<N> active`, or
+  `available via <provider>, suggest /god-automation-setup`
 - Security: `clear` or `sensitive files changed, suggest /god-harden`
 - Dependencies: `clear` or `dependency files changed, suggest /god-update-deps`
 - Hygiene: `fresh` or `stale, suggest /god-hygiene`

package/skills/god-version.md

@@ -16,7 +16,7 @@ Print version and a short capability summary.
 ```
 Godpowers v1.6.6
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 106 skills, 39 agents, 13 workflows, 36 recipes
+Surface: 108 skills, 39 agents, 13 workflows, 36 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 ```