godpowers 3.0.1 → 3.11.0

package/skills/god-scan.md

@@ -17,19 +17,15 @@ god-build, god-feature, god-hotfix etc. trigger automatically (per
 Phase 7 workflow integration). Useful when you want to refresh state
 between automatic triggers, or after manual code edits.
 
-Because `/god-scan` calls the local reverse-sync runtime directly, it must be
-explicit when no agent is spawned:
+Because `/god-scan` calls the local reverse-sync runtime directly, keep the
+default message concise:
 
 ```
-Auto-invoked:
-  Trigger: /god-scan
-  Agent: none, local runtime only
-  Local syncs:
-    + reverse-sync: pending
-  Artifacts: pending
-  Log: REVIEW-REQUIRED.md if drift is found
+Scanning code links and drift. Review items will be written to REVIEW-REQUIRED.md if found.
 ```
 
+Use a detailed `Auto-invoked:` card only with `--verbose` or debugging.
+
 ## Forms
 
 | Form | Action |

package/skills/god-spike.md

@@ -84,12 +84,11 @@ Suggested next:
   - If rejecting: archive .godpowers/spikes/<question-slug>/
   - If unclear: /god-spike with narrower question
 
-Proposition:
-  1. Implement partial: /god-feature for the smallest proven slice
-  2. Implement complete: /god-feature with the full recommendation
-  3. Discuss more: /god-discuss the remaining uncertainty
-  4. Run God Mode: /god-mode only if this spike unblocks the full project run
-Recommended: proceed only when SPIKE.md has a clear DECISION and evidence.
+Next commands:
+- /god-feature for the smallest proven slice: Run the smallest safe next step.
+- /god-feature with the full recommendation: Run the full recommended path.
+- /god-discuss the remaining uncertainty: Resolve the open question before continuing.
+- /god-mode only if this spike unblocks the full project run: Run the full autonomous project workflow when it fits.
 
 REMINDER: spike code is throwaway. Do NOT merge to main.
 ```

package/skills/god-standards.md

@@ -55,12 +55,11 @@ Suggested next:
   /god-redo prd to address failures with feedback
   /god-skip prd --reason "..." to accept-as-is
 
-Proposition:
-  1. Implement partial: /god-redo [tier] with the listed failures
-  2. Implement complete: fix all failures, rerun /god-standards, then continue the gate
-  3. Discuss more: /god-discuss standards failure
-  4. Skip: /god-skip [tier] --reason "..." only with an explicit reason
-Recommended: [one option and why]
+Next commands:
+- /god-redo [tier] with the listed failures: Run the smallest safe next step.
+- /god-standards [tier]: Re-run the standards gate after fixing all failures.
+- /god-discuss standards failure: Resolve the open question before continuing.
+- /god-skip [tier] --reason "..." only with an explicit reason: Skip only with an explicit reason.
 ```
 
 ## Auto-invocation

package/skills/god-status.md

@@ -20,6 +20,7 @@ proactive checks, blockers, planning visibility, and the next action first.
 | View | Shortcut | Purpose |
 |------|----------|---------|
 | Overview | `/god-status` | Operational state, proactive checks, and blockers. |
+| Full dashboard | `/god-status --full` | Complete dashboard and every proactive check. |
 | Progress ledger | `/god-progress` | Requirement and roadmap increment completion. |
 | Lifecycle phase | `/god-status --lifecycle` | Project phase and fitting workflows. |
 | Resume location | `/god-status --locate` | Orientation from checkpoint, handoff, and disk state. |
@@ -33,20 +34,21 @@ aliases for one minor release. New workflows should use `/god-status
 
 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)`.
+3. Call `dashboard.compute(projectRoot)` and render the compact action brief by default.
 4. Prefer the MCP `status` tool when it is available, and fall back to the CLI or runtime module when it is not.
-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.
+5. If `--full` is present, render the complete dashboard with all proactive checks.
+6. If `--lifecycle` is present, emphasize lifecycle phase, fitting workflows, PRD visibility, roadmap visibility, and the next route.
+7. If `--locate` is present, emphasize CHECKPOINT.md, HANDOFF.md, recent events, current step, and the next route.
+8. Use `.godpowers/PROGRESS.md` only as generated fallback or legacy explanation when state.json is missing.
+9. Scan canonical artifact paths for PRD, design, architecture, roadmap, stack, repo, build, deploy, observe, launch, harden, sync, checkpoint, and requirements evidence.
+10. Compare disk state to recorded state and flag phantom resume or untracked work.
+11. Offer `/god-repair` when recorded state and disk evidence conflict.
 
 ## Required reference
 
-Read `<runtimeRoot>/references/shared/DASHBOARD-CONTRACT.md` before rendering output. The shared contract owns the dashboard shape, proactive labels, and proposition block.
+Read `<runtimeRoot>/references/shared/DASHBOARD-CONTRACT.md` before rendering output. The shared contract owns the compact status shape, full dashboard shape, proactive labels, and `Next commands:` block.
 
-If the runtime module is unavailable, fall back to a manual scan and say `Dashboard engine: unavailable, manual scan used`.
+If the runtime module is unavailable, use a manual scan quietly and suggest `/god-doctor` only when the fallback changes the recommendation.
 
 Never mix workflow progress with audit, hygiene, remediation, or launch-readiness scores. Label those scores separately when they appear.
 
@@ -54,7 +56,7 @@ Never mix workflow progress with audit, hygiene, remediation, or launch-readines
 
 `/god-status` is read-only by default. It suggests Level 3 agents instead of spawning them unless the user asked status to continue work.
 
-Report checkpoint, review, sync, docs, repo surface, host, runtime, automation, security, dependency, and hygiene signals using the labels in the shared dashboard contract.
+Report checkpoint, review, sync, docs, repo surface, host, runtime, automation, security, dependency, and hygiene signals only when they affect the recommendation. `/god-status --full` shows every label from the shared dashboard contract.
 
 ## Mode D awareness
 

package/skills/god-surface.md

@@ -0,0 +1,61 @@
+---
+name: god-surface
+description: |
+  Preview or apply a runtime command surface profile after install. Lets users
+  switch between core, builder, maintainer, suite, and full without reinstalling
+  from scratch.
+
+  Triggers on: "god surface", "/god-surface", "switch command surface",
+  "change profile", "show fewer commands"
+---
+
+# /god-surface
+
+Preview or apply a runtime command surface profile after install. Use the
+existing installer profiles: `core`, `builder`, `maintainer`, `suite`, and
+`full`.
+
+## Process
+
+1. Resolve `<runtimeRoot>/lib/surface-profile.js`.
+2. Default to dry-run preview.
+3. Require an explicit runtime target such as `--codex`, `--claude`,
+   `--runtime=codex`, or `--all` before applying.
+4. Apply only when the user passes `--apply`.
+5. End with `Next commands:`.
+
+## Examples
+
+```bash
+/god-surface --profile=core --dry-run
+/god-surface --profile=builder --runtime=codex --dry-run
+/god-surface --profile=maintainer --runtime=claude --apply
+```
+
+Terminal equivalent:
+
+```bash
+npx godpowers surface --profile=builder --codex --global --dry-run
+npx godpowers surface --profile=builder --codex --global --apply
+```
+
+## Output Shape
+
+```text
+The builder profile would install the product-building command surface for Codex.
+
+Attention:
+- Dry-run only. No installed skills changed.
+
+Next commands:
+- /god-surface --profile=builder --runtime=codex --apply: Apply the previewed Codex surface.
+- /god-help: Open the compact help view after switching.
+- /god-help all: Show the complete catalog.
+```
+
+## Rules
+
+- Do not apply a profile unless the user explicitly asks with `--apply`.
+- Do not change project `.godpowers/` state.
+- Do not invent new profile names.
+- Keep the profile source of truth in `<runtimeRoot>/lib/install-profiles.js`.

package/skills/god-sync.md

@@ -57,18 +57,14 @@ User runs `/god-sync` after manual changes. Useful for:
    - Or: re-run reconciliation against current state to detect what changed
    - Recent commits for context
 
-Before spawning, show a visible auto-invoke card:
+Before spawning, show a concise sync note:
 
 ```
-Auto-invoked:
-  Trigger: <manual /god-sync, recipe closeout, /god-mode final sync, or other source>
-  Agent: god-updater
-  Local syncs:
-    - pending: feature-awareness, reverse-sync, source-sync, repo-doc-sync, repo-surface-sync, route-quality-sync, recipe-coverage-sync, release-surface-sync, pillars-sync, checkpoint-sync, context-refresh
-  Artifacts: pending
-  Log: .godpowers/SYNC-LOG.md
+Syncing project artifacts after this workflow. Details will be written to .godpowers/SYNC-LOG.md.
 ```
 
+Use the detailed helper list only with `--verbose` or release-gate debugging.
+
 ## Verification
 
 After god-updater returns:

package/skills/god-tech-debt.md

@@ -54,11 +54,10 @@ Suggested next:
   - /god-upgrade for major-version migrations
   - Re-run /god-tech-debt quarterly
 
-Proposition:
-  1. Implement partial: run the command for the top P0 item only
-  2. Implement complete: /god-feature or /god-refactor for the full P0 bundle
-  3. Discuss more: /god-discuss the highest-cost or highest-risk debt item
-  4. Run God Mode: /god-mode only if debt work should join the full project run
-Recommended: start with the top P0 item, then re-run /god-tech-debt after it
+Next commands:
+- /god-refactor <top-p0-item>: Address the highest-priority debt item first.
+- /god-feature or /god-refactor for the full P0 bundle: Run the full recommended path.
+- /god-discuss the highest-cost or highest-risk debt item: Resolve the open question before continuing.
+- /god-mode only if debt work should join the full project run: Run the full autonomous project workflow when it fits.
 lands.
 ```

package/skills/god-test-runtime.md

@@ -110,18 +110,14 @@ missing. If only a local URL is evidenced, run local verification and defer
 deployed staging verification until the user provides
 `STAGING_APP_URL=<deployed staging origin>` or reaches final sign-off.
 
-When auto-invoked, show:
+When auto-invoked, show a concise default note:
 
 ```text
-Auto-invoked:
-  Trigger: frontend-visible files changed and URL was evidenced
-  Agent: god-browser-tester
-  Local syncs:
-    + runtime-verification: <audit | test | full pipeline>
-  Artifacts: .godpowers/runtime/<run-id>/
-  Log: .godpowers/runtime/<run-id>/summary.md
+Verified the evidenced runtime target. Details were written to .godpowers/runtime/<run-id>/summary.md.
 ```
 
+Use a detailed `Auto-invoked:` card only with `--verbose` or debugging.
+
 ## Output to events.jsonl
 
 ```json

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: 117 skills, 40 agents, 13 workflows, 42 recipes
+Surface: 120 skills, 40 agents, 13 workflows, 43 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/skills/god.md

@@ -2,8 +2,9 @@
 name: god
 description: |
   Front door. Take free-text intent from the user, match it to a recipe via
-  the Godpowers runtime recipes module, and propose the matching command sequence. If no
-  text given, fall back to state-driven suggestion (same as /god-next Mode 3).
+  the Godpowers runtime recipes module, and recommend one matching command
+  sequence. If no text is given, show one state-derived recommendation and a
+  few alternatives.
 
   Triggers on: "/god", "god", "/god help", "I want to ...", "how do I ..."
   (when not matched by a more specific command)
@@ -12,10 +13,13 @@ description: |
 # /god (front door)
 
 The natural-language entry point. Users describe what they want; this skill
-matches the intent to a recipe and suggests the right command sequence. No
+matches the intent to a recipe and recommends the right command sequence. No
 agent is spawned here. This is a thin router on top of the Godpowers runtime
 recipes module.
 
+If the user only types `/god`, answer with one sentence of position, one
+recommended command, and 2 to 3 alternatives. Do not show a catalog.
+
 ## Runtime module resolution
 
 Before calling runtime modules, resolve the Godpowers runtime root:
@@ -31,13 +35,14 @@ Recipes are scenario-shaped ("I'm coming back after a week", "production is
 broken", "add a feature during the current project run") and match free-text intent. `/god` is the
 front door that turns intent into the right slash command.
 
-This skill complements `/god-next` rather than replacing it:
+This skill is the single front door. It points to narrower views only when the
+user needs them:
 
 | Skill | Best for |
 |-------|----------|
 | `/god <free text>` | "I don't know which command, but here's what I want" |
-| `/god-next` | "I just finished X, what's next?" or pre-flight checks |
-| `/god-status` | "Where are we? what's done?" |
+| `/god-next` | "Continue safely from disk state" |
+| `/god-status --full` | "Show every dashboard detail" |
 | `/god-init` | "Start a project here" |
 | `/god-mode` | "Run the whole project run autonomously" |
 
@@ -110,9 +115,10 @@ Treat everything after `/god` as free text. If empty, treat as state-driven.
 
 ```
 text empty?
-  yes -> state-driven: call <runtimeRoot>/lib/recipes.js suggestForState(projectRoot)
-         display top 3 recipes ranked by current lifecycle phase
-         also call <runtimeRoot>/lib/router.js suggestNext(projectRoot) for structural next
+  yes -> state-driven: call <runtimeRoot>/lib/dashboard.js compute(projectRoot)
+         display one sentence of current position
+         recommend the structural next command first
+         show at most 3 alternatives
 
   no  -> intent-driven: call <runtimeRoot>/lib/recipes.js matchIntent(text, projectRoot)
          call <runtimeRoot>/lib/command-families.js classifiers for capture, work size, verification, and trigger precedence hints
@@ -127,15 +133,18 @@ text empty?
 For a single high-confidence match (score >= 10):
 
 ```
-Best match: <recipe.metadata.name>
-What this does: <recipe.metadata.description>
+Recommended: <command>
+Why: <one sentence tied to the user's words and disk state>
 
 Sequence:
   1. <command>   <why>
   2. <command>   <why>
   ...
 
-Run this sequence? (yes / show others / cancel)
+Next commands:
+- <command>: Run the recommended sequence.
+- /god-help <family>: See only the relevant family.
+- /god-status --full: Inspect the complete dashboard first.
 ```
 
 For multiple matches (top 3):
@@ -147,38 +156,27 @@ Top matches for "<user text>":
   2. <recipe-name>   (<score>)   <description>
   3. <recipe-name>   (<score>)   <description>
 
-Pick one (1/2/3) or describe more specifically.
+Next commands:
+- <best command>: Run the strongest match.
+- /god-discuss <ambiguity>: Resolve the routing ambiguity.
+- /god-help <family>: See the relevant command family.
 ```
 
 For state-driven (no text):
 
 ```
-Where you are: <lifecycle-phase>
-
-Structural next: <command>   <why>
-
-Recipes that fit your current state:
-  - <recipe-name>   <description>
-  - <recipe-name>   <description>
+You are <lifecycle-phase>; the likely next move is <command>.
 
-Run structural next? (yes / pick recipe / cancel)
-```
-
-If the answer is exploratory and proposes an approach instead of selecting or
-running a command, close with:
-
-```
-Proposition:
-  1. Implement partial: <smallest safe command or slice>
-  2. Implement complete: <full command sequence>
-  3. Discuss more: /god-discuss <topic or unresolved question>
-  4. Run God Mode: /god-mode <scope> if the user wants the full autonomous project run
-Recommended: <one option and why>
+Next commands:
+- <command>: <why>
+- /god-next: Continue with the state-derived safe step.
+- /god-status --full: Inspect every dashboard check.
+- /god-help all: Show the complete catalog.
 ```
 
 Do not include a God Mode option when the request is clearly a tiny fix,
-single-file change, or narrow question. In that case, replace it with the
-smallest matching command, such as `/god-fast`, `/god-spike`, or `/god-next`.
+single-file change, or narrow question. In that case, recommend the smallest
+matching command, such as `/god-fast`, `/god-spike`, or `/god-next`.
 
 ### Step 4: execute or hand off
 
@@ -218,7 +216,10 @@ What this does: Production is broken now
 Sequence:
   1. /god-hotfix     Skip planning, debug, fix with TDD, expedited deploy, schedule postmortem
 
-Run this sequence? (yes / show others / cancel)
+Next commands:
+- /god-hotfix: Start the expedited production fix.
+- /god-help operate: See production operations commands only.
+- /god-status --full: Inspect the complete dashboard first.
 ```
 
 ### Example 2: ambiguous intent (multiple matches)
@@ -228,10 +229,13 @@ User: /god parallel feature during build
 
 Top matches for "parallel feature during build":
 
-  1. add-feature-mid-arc-pause       (10)   Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume
-  2. add-feature-parallel            (10)   Parallel feature, do not disrupt main work
+  1. feature-during-current-work     (10)   Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume
+  2. parallel-feature                (10)   Parallel feature, do not disrupt main work
 
-Pick one (1/2) or describe more specifically.
+Next commands:
+- /god-reconcile parallel feature during build: Resolve the roadmap impact first.
+- /god-feature parallel feature: Start the feature as scoped work.
+- /god-discuss parallel feature routing: Clarify which path fits.
 ```
 
 ### Example 3: state-driven (no text)
@@ -239,16 +243,12 @@ Pick one (1/2) or describe more specifically.
 ```
 User: /god
 
-Where you are: tier-1 in progress (PRD done, ARCH pending)
-
-Structural next: /god-arch
-Why: PRD is complete; architecture is the next gate
-
-Recipes that fit your current state:
-  - whats-next                Show the next logical step with reason
-  - rerun-tier                Redo a previous tier with new inputs
+You are in planning with the PRD done and architecture pending.
 
-Run /god-arch? (yes / pick recipe / cancel)
+Next commands:
+- /god-arch: Start the next planning gate.
+- /god-status --full: Inspect all dashboard details first.
+- /god-help start: See start and planning commands only.
 ```
 
 ### Example 4: no match
@@ -258,11 +258,12 @@ User: /god make me a sandwich
 
 No recipe matched. Falling back to state-driven suggestion.
 
-Where you are: tier-3 launched
-Structural next: (none, project run complete)
+You are launched and no recipe matched the request.
 
-Suggested: /god-next   show all valid next-step options
-       or: /god-status   re-derive state from disk
+Next commands:
+- /god-next: Continue from disk state.
+- /god-status --full: Re-derive full status from disk.
+- /god-discuss routing ambiguity: Clarify what you want Godpowers to do.
 ```
 
 ## Why a skill, not an agent