godpowers 3.0.0 → 3.0.2

package/skills/god-prd.md

@@ -82,6 +82,4 @@ The reflog records every god-prd invocation as `op:god-prd` for `/god-undo`.
   for `/god-repair` review. Re-running picks up cleanly.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-preflight.md

@@ -137,18 +137,17 @@ Use the report to choose the next pass:
 | Tests are absent before refactor | `/god-add-tests` |
 | Refactor path is obvious and bounded | `/god-refactor` |
 
-## Proposition Closeout
+## Next Commands Closeout
 
-End the user-facing response with a proposition block based on the recommended
+End the user-facing response with a Next commands block based on the recommended
 sequence:
 
 ```
-Proposition:
-  1. Implement partial: [first recommended command or task]
-  2. Implement complete: [full recommended sequence]
-  3. Discuss more: /god-discuss [highest uncertainty or blocker]
-  4. Run God Mode: /god-mode only when the preflight says the repo is ready or the remaining gaps are acceptable
-Recommended: [first command and why it should happen before the rest]
+Next commands:
+- /god-next: Run the first recommended command from the preflight result.
+- /god-mode: Continue the full recommended sequence when preflight is clear.
+- /god-discuss [highest uncertainty or blocker]: Resolve the open question before continuing.
+- /god-mode only when the preflight says the repo is ready or the remaining gaps are acceptable: Run the full autonomous project workflow when it fits.
 ```
 
 ## Guardrails

package/skills/god-progress.md

@@ -78,17 +78,16 @@ Open the full checklist any time: .godpowers/REQUIREMENTS.md
 Use plain text. No emoji, no box-drawing. Ledger marks are `[x]` done, `[~]`
 in progress, `[ ]` not started, matching the ledger file.
 
-## Proposition Closeout
+## Next Commands Closeout
 
-End every progress report with a proposition block:
+End every progress report with a Next commands block:
 
 ```text
-Proposition:
-  1. Implement partial: [single next command, e.g. /god-build]
-  2. Implement complete: /god-mode to continue the project run when unblocked
-  3. Inspect deeper: open .godpowers/REQUIREMENTS.md or run /god-status
-  4. Discuss more: /god-discuss [a gap, a blocked requirement, or scope]
-Recommended: [one option and one sentence on why it fits the disk state]
+Next commands:
+- /god-build: Continue the next build step when the roadmap is unblocked.
+- /god-mode: Continue the project run when the current phase is safe to resume.
+- /god-status --full: Inspect the complete dashboard and proactive checks.
+- /god-discuss <blocked requirement>: Resolve a gap before continuing.
 ```
 
 If `derived.gaps` is non-empty, make `/god-review-changes` (or fixing the gap)

package/skills/god-reconcile.md

@@ -83,12 +83,11 @@ Recommended sequence:
   Main work:  [/god-feature scoped to Milestone 2]
   Post-work:  [/god-sync]
 
-Proposition:
-  1. Implement partial: [run only the first preflight command]
-  2. Implement complete: [run the full recommended sequence]
-  3. Discuss more: /god-discuss [ambiguous overlap or artifact conflict]
-  4. Cancel: leave artifacts unchanged
-Recommended: [one option and why]
+Next commands:
+- /god-next: Run only the first preflight command.
+- /god-sync: Run the full recommended sync sequence after reconciliation.
+- /god-discuss [ambiguous overlap or artifact conflict]: Resolve the open question before continuing.
+- stop: Leave artifacts unchanged.
 ```
 
 ## Difference from /god-roadmap-check
@@ -97,8 +96,8 @@ Recommended: [one option and why]
 |---|---|---|
 | Scope | ROADMAP only | Core artifacts plus runtime and repository surfaces |
 | Use | Quick check | Comprehensive |
-| Auto-invoked | by feature-addition recipes (legacy) | by feature-addition recipes (preferred) |
-| Replaces | -- | /god-roadmap-check (kept for back-compat) |
+| Auto-invoked | legacy compatibility only | by feature-addition recipes |
+| Replaces | delegated to /god-reconcile | primary command |
 
-For new projects, prefer /god-reconcile. /god-roadmap-check remains a
-narrower tool for when you only care about milestone overlap.
+For new projects, use /god-reconcile. /god-roadmap-check remains a
+compatibility alias that asks `god-reconciler` for ROADMAP-focused output.

package/skills/god-reconstruct.md

@@ -59,13 +59,11 @@ Suggested next:
   /god-feature     - now you can add features with reconciliation
   /god-tech-debt   - assess what needs paying down
 
-Proposition:
-  1. Implement partial: /god-audit the reconstructed artifacts first
-  2. Implement complete: /god-audit then /god-feature with reconciliation
-  3. Discuss more: /god-discuss stakeholder review questions
-  4. Run God Mode: /god-mode after stakeholder review or audit accepts the reconstruction
-Recommended: /god-audit before new feature work because reconstruction is
-evidence-derived, not stakeholder-approved.
+Next commands:
+- /god-audit the reconstructed artifacts first: Run the smallest safe next step.
+- /god-audit then /god-feature with reconciliation: Run the full recommended path.
+- /god-discuss stakeholder review questions: Resolve the open question before continuing.
+- /god-mode after stakeholder review or audit accepts the reconstruction: Run the full autonomous project workflow when it fits.
 ```
 
 ## Caveats

package/skills/god-redo.md

@@ -57,6 +57,4 @@ that originally produced the artifact. Updates the linkage map via
 `/god-scan` after the artifact is rewritten.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-refactor.md

@@ -92,18 +92,17 @@ Suggested next: /god-status or continue with /god-feature
 
 When the user asks for a proposal, recommendation, or performance-improvement
 approach and no files are edited, do not stop after the advice. End with a
-proposition block that turns the recommendation into user-selectable next
+Next commands block that turns the recommendation into user-selectable next
 moves.
 
 Use this shape:
 
 ```
-Proposition:
-  1. Implement partial: /god-spike <measurement or smallest safe slice>
-  2. Implement complete: /god-refactor <full scoped refactor>
-  3. Discuss more: /god-discuss <unresolved scope question>
-  4. Run God Mode: /god-mode <scope> if the user wants the full autonomous project run
-Recommended: <one option and why>
+Next commands:
+- /god-spike <measurement or smallest safe slice>: Run the smallest safe next step.
+- /god-refactor <full scoped refactor>: Run the full recommended path.
+- /god-discuss <unresolved scope question>: Resolve the open question before continuing.
+- /god-mode <scope> if the user wants the full autonomous project run: Run the full autonomous project workflow when it fits.
 ```
 
 For performance refactors, prefer partial implementation when measurement is
@@ -144,6 +143,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-repair.md

@@ -66,6 +66,4 @@ Built-in. Reads + writes:
 Calls into `lib/drift-detector.js`, `lib/code-scanner.js`, `lib/reverse-sync.js`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-repo.md

@@ -34,6 +34,4 @@ Suggested next: /god-build (start building the first milestone)
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-restore.md

@@ -75,6 +75,4 @@ files back via standard fs operations. Calls `/god-scan` after restore
 to refresh linkage map.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-roadmap-check.md

@@ -18,12 +18,13 @@ description: |
 Deprecated: prefer `/god-reconcile` for new workflows. This command remains in
 the full profile for backward compatibility with existing route references.
 
-Reconcile intent against ROADMAP.md before adding work.
+Reconcile intent against ROADMAP.md before adding work. This legacy command
+delegates to `god-reconciler` with ROADMAP-focused output.
 
 ## Setup
 
 1. Verify `.godpowers/roadmap/ROADMAP.md` exists. If not: nothing to reconcile against; suggest /god-roadmap or /god-feature directly.
-2. Spawn god-roadmap-reconciler with the user's intent description and the roadmap path.
+2. Spawn `god-reconciler` with the user's intent description and ask for ROADMAP-focused output.
 
 ## Output
 
@@ -59,19 +60,18 @@ For each status, the recommendation differs:
 
 ## Verification
 
-After god-roadmap-reconciler returns:
+After `god-reconciler` returns:
 1. Verify the verdict has a status from the canonical 6
 2. Verify recommendation has a concrete action
 3. Display to user; await decision before proceeding
-4. End with a proposition block:
+4. End with a Next commands block:
 
 ```
-Proposition:
-  1. Implement partial: [smallest command from the recommendation]
-  2. Implement complete: [roadmap update plus feature work when needed]
-  3. Discuss more: /god-discuss roadmap overlap
-  4. Defer: /god-add-backlog [intent]
-Recommended: [one option and why]
+Next commands:
+- /god-roadmap-update: Apply the smallest roadmap correction from the recommendation.
+- /god-feature <feature-name>: Start feature work after roadmap overlap is clear.
+- /god-discuss roadmap overlap: Resolve the open question before continuing.
+- /god-add-backlog [intent]: Defer the work for later review.
 ```
 
 ## When called manually

package/skills/god-roadmap.md

@@ -62,6 +62,4 @@ The reflog records every god-roadmap invocation as `op:god-roadmap` for `/god-un
   for `/god-repair` review. Re-running picks up cleanly.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-rollback.md

@@ -72,6 +72,4 @@ Writes via `lib/reverse-sync.js` (for linkage truncation) and standard
 fs operations (for artifact move).
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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 |
@@ -114,6 +110,4 @@ User content outside fences is never modified.
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-skip.md

@@ -62,6 +62,4 @@ Reverse a previous skip. Marks the sub-step `pending` again.
 Built-in. Reads and writes `state.json`, regenerates the managed progress view, and appends to reflog.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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-stack.md

@@ -59,6 +59,4 @@ The reflog records every god-stack invocation as `op:god-stack` for `/god-undo`.
   for `/god-repair` review. Re-running picks up cleanly.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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-story-build.md

@@ -60,6 +60,4 @@ Reverse-sync writes Implementation Linkage footer to ROADMAP.md
   still fires)
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story-close.md

@@ -66,6 +66,4 @@ linkage updates.
 - Trigger any other workflow automatically
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story.md

@@ -39,6 +39,4 @@ Add a new story under `.godpowers/stories/<feature-slug>/`.
 - `/god-stories` to see all stories
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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

@@ -43,7 +43,7 @@ User runs `/god-sync` after manual changes. Useful for:
    payload, agent handoffs, workflow metadata, recipe routes, extension packs,
    route quality, recipe coverage, release surfaces, and release policy are
    checked before sync closes. Structural drift should recommend scoped agents
-   such as `god-auditor`, `god-roadmap-reconciler`, `god-coordinator`, or
+   such as `god-auditor`, `god-reconciler`, `god-coordinator`, or
    `god-docs-writer`.
 6. If repo documentation changed durable project truth, plan or apply Pillars
    updates through `lib/pillars.planArtifactSync` or
@@ -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:
@@ -94,7 +90,7 @@ Sync status:
     + repo-doc-sync: <refreshed README badges/counts, recommended god-docs-writer, or no-op>
     + repo-surface-sync: <checked routes/package/agents/workflows/extensions, recommended scoped agents, or no-op>
     + route-quality-sync: <checked atomic spawns and typed route outcomes, no-op, or recommended god-auditor>
-    + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-roadmap-reconciler>
+    + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-reconciler>
     + release-surface-sync: <checked badges/changelog/release/package guards, no-op, or recommended god-docs-writer>
     + pillars-sync: <updated N pillar files, no-op, or proposed>
     + checkpoint-sync: <CHECKPOINT.md updated or skipped>
@@ -154,6 +150,4 @@ Both bookends run automatically in feature-addition recipes. Both can be
 invoked manually for spot-checks.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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-undo.md

@@ -52,6 +52,4 @@ Suggested next:
 ```
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-update-deps.md

@@ -120,6 +120,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-upgrade.md

@@ -123,6 +123,4 @@ in the linkage system:
   via `/god-review-changes`.
 
 
-## Locking
-
-See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.
+Locking: See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

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