godpowers 1.6.8 → 1.6.10

package/skills/god-hotfix.md

@@ -17,7 +17,7 @@ Urgent production bug fix. Speed matters; discipline still applies.
 
 - Production is broken or degraded
 - Users are affected right now
-- Waiting for a normal /god-mode arc is unacceptable
+- Waiting for a normal /god-mode project run is unacceptable
 
 ## When NOT to use
 

package/skills/god-hygiene.md

@@ -23,7 +23,7 @@ Periodic health check. Three audits in one slash command.
 ## When NOT to use
 
 - Mid-incident: focus on /god-hotfix or /god-debug
-- Right after /god-mode: hygiene was already optional during arc
+- Right after /god-mode: hygiene was already optional during the project run
 
 ## Orchestration
 
@@ -93,6 +93,13 @@ Suggested next actions (in priority order):
   3. [next]
 
 Schedule next hygiene check in [N days] (default: 30).
+
+Proposition:
+  1. Implement partial: [highest-priority action]
+  2. Implement complete: [all P0/P1 hygiene actions in order]
+  3. Discuss more: /god-discuss hygiene remediation
+  4. Inspect status: /god-status after fixes
+Recommended: [one option and why]
 ```
 
 ## Have-Nots

package/skills/god-init.md

@@ -260,5 +260,5 @@ without explicit user invocation of /god-suite-init.
 After init completes, print:
 
 ```
-Suggested next: /god-prd for requirements, or /god-mode for the full autonomous arc.
+Suggested next: /god-prd for requirements, or /god-mode for the full autonomous project run.
 ```

package/skills/god-launch.md

@@ -58,7 +58,7 @@ the user requests staging or final sign-off begins.
 The launch pause must not expand into every possible channel, analytics, or
 provider credential. Ask only for the next missing access item needed to run a
 named live smoke, launch-readiness, attribution, or monitoring check. Do not
-ask mid-arc for `STAGING_APP_URL` unless the user requested deployed staging.
+ask mid-run for `STAGING_APP_URL` unless the user requested deployed staging.
 At final sign-off, if no live target URL is known, ask only for
 `STAGING_APP_URL=<staging-origin>`.
 

package/skills/god-lifecycle.md

@@ -17,7 +17,7 @@ Show project phase and contextually appropriate workflows.
 
 1. Detect lifecycle phase from disk:
    - **No `.godpowers/`** -> Pre-init
-   - **`.godpowers/PROGRESS.md` exists, not all tiers done** -> In-arc
+   - **`.godpowers/PROGRESS.md` exists, not all tiers done** -> In progress
    - **All tiers done, no special markers** -> Steady state
    - **`.godpowers/postmortems/<id>/` exists with no POSTMORTEM.md** -> Post-incident pending
    - **`.godpowers/migrations/<slug>/MIGRATION.md` exists, status != complete** -> In-migration
@@ -36,15 +36,18 @@ Lifecycle: Pre-init (no Godpowers project here)
 Available actions:
   /god-init     Initialize a Godpowers project
   /god-explore  Brainstorm before committing
-  /god-mode     Run full autonomous arc (will init first)
+  /god-mode     Run full autonomous project run (will init first)
 ```
 
-### In-arc
+### In Progress
 ```
-Lifecycle: In-arc (planning/building/shipping)
+Lifecycle: In progress (planning/building/shipping)
 
 Current state:
   PRD:          [done/pending]
+  Roadmap:      [done/pending]
+  Current step: [phase, tier, or roadmap milestone]
+  Completion:   [pct]% ([done] of [total] tracked steps)
   Architecture: [done/pending]
   ...
 
@@ -55,7 +58,7 @@ Or run /god-mode to autonomously continue from here.
 
 ### Steady state
 ```
-Lifecycle: Steady state (full-arc complete, in maintenance)
+Lifecycle: Steady state (project run complete, in maintenance)
 
 Last full audit: [N days ago]
 Last dep audit: [N days ago]
@@ -111,6 +114,31 @@ Suggested next: /god-spike with narrower question
 Or: archive the spike if no longer relevant
 ```
 
+## Proposition Closeout
+
+Every lifecycle report must end with a proposition block. Use the detected
+phase to fill in concrete commands:
+
+```
+Proposition:
+  1. Implement partial: [smallest safe next command from the lifecycle report]
+  2. Implement complete: /god-mode [resume or scope] when the phase is safe for an autonomous project run
+  3. Discuss more: /god-discuss [unclear phase, blocker, or choice]
+  4. Inspect status: /god-status or /god-next
+Recommended: [one option and why it matches the detected phase]
+```
+
+For hard blockers, such as post-incident pending, replace the broad options
+with the required next command plus inspect and discuss alternatives:
+
+```
+Proposition:
+  1. Resolve required next: /god-postmortem
+  2. Inspect first: /god-status
+  3. Discuss blocker: /god-discuss incident follow-up
+Recommended: /god-postmortem because the incident learning loop is still open.
+```
+
 ## Have-Nots
 
 Lifecycle check FAILS if:

package/skills/god-list-assumptions.md

@@ -48,6 +48,19 @@ Assumptions Claude is operating under:
 Any of these wrong? Flag them now before they cement into decisions.
 ```
 
+## Proposition Closeout
+
+After listing assumptions, end with a proposition block:
+
+```
+Proposition:
+  1. Implement partial: correct or confirm the low-confidence assumptions only
+  2. Implement complete: confirm assumptions and continue to [queued command]
+  3. Discuss more: /god-discuss assumptions before planning
+  4. Inspect status: /god-status to re-ground before deciding
+Recommended: [one option and why]
+```
+
 ## Have-Nots
 
 - Assumptions are too vague to verify ("we're building a good product")

package/skills/god-locate.md

@@ -73,6 +73,22 @@ Drift check:
 - If gap > 1 hour, run /god-context-scan
 ```
 
+## Proposition Closeout
+
+The orientation summary must end with a compact proposition block:
+
+```
+Proposition:
+  1. Implement partial: [next suggested command]
+  2. Implement complete: /god-mode to continue the project run when no drift is flagged
+  3. Discuss more: /god-discuss [unclear state or stale checkpoint]
+  4. Inspect status: /god-status for the full report
+Recommended: [one option and why]
+```
+
+If drift is flagged, recommend `/god-context-scan` or `/god-repair` before
+continuing work.
+
 ## Process
 
 1. If `.godpowers/` does not exist: report "no Godpowers project here"

package/skills/god-logs.md

@@ -3,7 +3,7 @@ name: god-logs
 description: |
   View events.jsonl as a readable timeline. Each line: timestamp,
   event name, tier, agent, duration if available. Use to inspect
-  what happened during a run, debug a stuck arc, or audit
+  what happened during a run, debug a stuck project run, or audit
   retroactively.
 
   Triggers on: "god logs", "/god-logs", "show logs", "what happened",

package/skills/god-map-codebase.md

@@ -42,4 +42,12 @@ Codebase mapped.
   + .godpowers/codebase/concerns.md
 
 Suggested next: /god-init Mode B (gap-fill) or /god-feature
+
+Proposition:
+  1. Implement partial: /god-intel or /god-tech-debt on the riskiest mapped area
+  2. Implement complete: /god-init Mode B to gap-fill project artifacts
+  3. Discuss more: /god-discuss the unclear architecture or quality findings
+  4. Run God Mode: /god-mode after Mode B context exists
+Recommended: /god-init Mode B when the codebase is real but Godpowers artifacts
+are missing.
 ```

package/skills/god-mode.md

@@ -1,7 +1,7 @@
 ---
 name: god-mode
 description: |
-  Full autonomous arc orchestrator. Spawns the god-orchestrator agent in a
+  Full autonomous project-run orchestrator. Spawns the god-orchestrator agent in a
   fresh context which runs the entire workflow: idea to hardened production.
   Pauses only for legitimate human-only decisions.
 
@@ -12,11 +12,12 @@ description: |
 # /god-mode
 
 You are receiving a /god-mode invocation. Your job is to spawn the
-**god-orchestrator** agent in a fresh context to run the autonomous arc.
+**god-orchestrator** agent in a fresh context to run the autonomous project
+workflow.
 
 ## Process
 
-1. Resolve whether this is a new arc or a resume:
+1. Resolve whether this is a new project run or a resume:
    - If `.godpowers/state.json`, `.godpowers/PROGRESS.md`, or
      `.godpowers/CHECKPOINT.md` exists, this is a resume. Do not ask the user
      to describe the project again. Call
@@ -64,7 +65,7 @@ You are receiving a /god-mode invocation. Your job is to spawn the
      `workflows/<name>.yaml`, run via `lib/workflow-runner`)
    - `--plan` (v0.14; emit plan to `.godpowers/runs/<id>/plan.yaml`
      and stop. Same effect as `--dry-run`. Use with `--workflow` for
-     a specific arc's plan.)
+     a specific project run's plan.)
    - `--brownfield` (force brownfield path even if detection says greenfield)
    - `--bluefield` (force bluefield path)
    - `--greenfield` (force greenfield, skip archaeology even if code exists)
@@ -89,16 +90,16 @@ You are receiving a /god-mode invocation. Your job is to spawn the
        `/god-arch` when initial findings, imported planning context, the PRD,
        or the codebase show UI or product-experience signals
      - Instruction that a red test, typecheck, lint, build, or check command
-       is not a completed arc. It must enter the autonomous repair loop and
+       is not a completed project run. It must enter the autonomous repair loop and
        continue the same `/god-mode` run until green, except for Critical
        security or a genuine human-only decision.
      - Instruction that deploy, observe, harden, and launch must follow the
        Shipping Closure Protocol: verify a real environment when available,
        otherwise create local/CI-verifiable deploy automation, defer deployed
        staging by default, and continue until the user requests staging or the
-       arc reaches final sign-off.
+       project run reaches final sign-off.
      - Instruction that keys, API tokens, dashboards, admin consoles, and
-       provider-specific access are last-mile inputs. Do not pause mid-arc for
+       provider-specific access are last-mile inputs. Do not pause mid-run for
        `STAGING_APP_URL` unless the user requested deployed staging. At final
        sign-off, ask only for the smallest next item needed by a concrete
        command, usually `STAGING_APP_URL=<staging-origin>`. Ask for additional
@@ -114,7 +115,7 @@ You are receiving a /god-mode invocation. Your job is to spawn the
        artifact rewrites, and updates every affected artifact after approval.
      - Instruction that brownfield and bluefield arcs run `/god-preflight`
        automatically when `.godpowers/preflight/PREFLIGHT.md` is absent.
-       Greenfield arcs skip preflight unless the user explicitly requests it.
+       Greenfield project runs skip preflight unless the user explicitly requests it.
      - Instruction to run routing prerequisites through `lib/router.js`
        `checkPrerequisites` before every direct command dispatch. If
        `safe-sync-clear` fails, run
@@ -129,7 +130,7 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - Name the project root.
    - Name the invocation flags.
    - Name the handoff file path.
-   - Say: "Read the handoff file first, then run the autonomous arc from disk
+   - Say: "Read the handoff file first, then run the autonomous workflow from disk
      state. Return only user-facing progress and final status."
 
    Do not put recovered checkpoint facts, safe-sync plans, local file lists,
@@ -141,12 +142,12 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    loadout lists, or internal routing payloads into the user-visible transcript.
    The visible transcript may say only what phase is running, what durable state
    was detected, what commands are running, what changed, and the final
-   `Arc complete` or `PAUSE: external access required` block.
+   `Project run complete` or `PAUSE: external access required` block.
 
 8. Orchestrator runs the appropriate workflow:
-   - Greenfield -> full-arc
-   - Brownfield -> brownfield-arc (preflight -> archaeology -> reconstruct -> debt-assess -> greenfield simulation audit -> greenfieldify plan and approved artifact updates -> proceed)
-   - Bluefield -> bluefield-arc (org-context -> preflight -> greenfield simulation audit -> greenfieldify plan and approved artifact updates -> arc with constraints)
+   - Greenfield -> full project run
+   - Brownfield -> brownfield project run (preflight -> archaeology -> reconstruct -> debt-assess -> greenfield simulation audit -> greenfieldify plan and approved artifact updates -> proceed)
+   - Bluefield -> bluefield project run (org-context -> preflight -> greenfield simulation audit -> greenfieldify plan and approved artifact updates -> workflow with constraints)
 
 9. Relay only the orchestrator's user-facing output to the user. If the
    platform displays raw spawn details automatically, the displayed payload
@@ -168,9 +169,15 @@ Show:
 - detected resume or project mode in plain language
 - a compact "Next step" card before each visible phase or tier sub-step
 - a compact "Step result" card after each visible phase or tier sub-step
+- plain-language workflow names. Say "project run" or "workflow" instead of
+  unexplained "arc" in visible output
+- PRD and roadmap visibility in status and closeout blocks when artifacts
+  exist or are expected
 - short progress updates for phases, commands, validations, and file edits
 - concise validation summaries instead of full command noise when possible
 - final changed paths, validation results, and completion or pause status
+- final current status, open items, worktree/index state, and recommended next
+  action
 
 Hide:
 - raw Task input
@@ -280,7 +287,7 @@ complete. This ensures all 14 artifact categories are in a consistent state:
 
 - 10 Tier 0-3 artifacts validated (have-nots passing)
 - 4 capture artifacts noted as `not-yet-created` (graceful handling)
-- SYNC-LOG.md updated with arc completion entry
+- SYNC-LOG.md updated with project-run completion entry
 - state.json reflects final tier statuses
 
 Under `--yolo`, the sync step auto-applies (no pause). Under
@@ -297,7 +304,7 @@ If `/god-mode` resumes an existing `.godpowers` project that lacks Pillars,
 it Pillar-izes the project before continuing. Existing `.godpowers` artifacts
 become managed source references in the relevant `agents/*.md` files.
 
-The sync step is what closes the loop between greenfield arc creation and
+The sync step is what closes the loop between greenfield project-run creation and
 the comprehensive 14-artifact reconciliation system. See
 `docs/greenfield-coverage.md` for what's created when.
 
@@ -306,7 +313,19 @@ the comprehensive 14-artifact reconciliation system. See
 When orchestrator returns "complete", display:
 
 ```
-Godpowers full-arc complete.
+Godpowers project run complete.
+
+Current status:
+  State: complete
+  Progress: <pct>% (<done> of <total> steps complete; current step <n> of <total>)
+  Worktree: <clean | modified files unstaged | staged changes | mixed>
+  Index: <untouched | staged files listed>
+
+Planning visibility:
+  PRD: <done | pending | missing | deferred> <artifact path when present>
+  Roadmap: <done | pending | missing | deferred> <artifact path when present>
+  Current milestone: <roadmap milestone, tier, or next planning gate when known>
+  Completion: <pct>% <brief basis, for example done steps over total tracked steps>
 
 Artifacts on disk:
   + PRD           .godpowers/prd/PRD.md
@@ -337,5 +356,24 @@ Periodic hygiene:
   Quality audit:          /god-audit
   Health check:           /god-hygiene
 
-Or describe what you want and /god-next will route.
+Open items:
+  1. <none, or deployed staging deferred, pending review, unstaged files, etc.>
+
+Next:
+  Recommended: <single safest command or decision>
+  Why: <one sentence tied to disk state>
+
+Proposition:
+  1. Review status: /god-status
+  2. Continue work: /god-next or describe the next intent
+  3. Commit release-ready changes: stage only the intended files, then commit
+  4. Run deployed staging: provide STAGING_APP_URL=<deployed staging origin> when needed
 ```
+
+If the run edited code but did not stage or commit, the completion block must
+say so. If unrelated or pre-existing worktree changes are present, do not imply
+the worktree is clean. Recommend a scoped review or explicit staging path.
+
+If the run is a focused brownfield/refactor workflow rather than a full greenfield
+project run, adapt the same closeout shape and replace "Project is now in STEADY
+STATE" with the actual disk-derived lifecycle and next route.

package/skills/god-next.md

@@ -158,6 +158,16 @@ Path ahead:
 
 Keep the route to 3 lines unless the user asks for the full plan.
 
+Also show planning visibility when the artifacts exist or are expected:
+
+```
+Planning visibility:
+  PRD: <done | pending | missing> <path when present>
+  Roadmap: <done | pending | missing> <path when present>
+  Current milestone: <roadmap milestone, tier, or next planning gate>
+  Completion: <pct>% <basis from state.json or PROGRESS.md>
+```
+
 ## Process for Mode 4 (intent-based)
 
 ```
@@ -175,9 +185,9 @@ Returns ranked recipes matching:
 Display top match with the recipe's sequence:
    "Best match: add-feature-mid-arc-pause
     Sequence:
-      1. /god-pause-work  (Save current /god-mode arc state)
+      1. /god-pause-work  (Save current /god-mode project-run state)
       2. /god-feature     (Run feature workflow)
-      3. /god-resume-work (Restore arc)
+      3. /god-resume-work (Restore project run)
     
     Run this sequence? Or see other matches?"
 ```
@@ -277,13 +287,13 @@ When in steady state, match keywords to workflows:
 | upgrade, migrate, bump major | /god-upgrade |
 | docs, documentation, README | /god-docs |
 | deps, dependencies, audit | /god-update-deps |
-| preflight, intake, audit before arc-ready, audit before pillars | /god-preflight |
+| preflight, intake, audit before project run readiness, audit before pillars | /god-preflight |
 | audit, score, quality check | /god-audit |
 | health check, hygiene | /god-hygiene |
 
 If mode detection indicates brownfield or bluefield and
 `.godpowers/preflight/PREFLIGHT.md` is missing, prefer `/god-preflight` before
-recommending archaeology, reconstruction, arc-ready, pillars, or refactor work.
+recommending archaeology, reconstruction, project-run readiness, pillars, or refactor work.
 
 ## Output Format
 
@@ -312,3 +322,21 @@ Previous tier had standards failures. Address before proceeding:
   - [failure 2]
 Suggested: /god-redo [tier] OR /god-skip [tier] --reason="..."
 ```
+
+## Proposition Closeout
+
+Every `/god-next` response must end with a proposition block unless it already
+launched the selected command:
+
+```
+Proposition:
+  1. Implement partial: [single suggested command]
+  2. Implement complete: [recipe sequence or /god-mode when safe]
+  3. Discuss more: /god-discuss [routing ambiguity or missing prerequisite]
+  4. Inspect status: /god-status or /god-locate
+Recommended: [one option and why]
+```
+
+For missing prerequisites, the partial option is the auto-completable
+prerequisite. For standards failures, the partial option is `/god-redo` with
+feedback and the complete option is blocked until the gate passes.

package/skills/god-org-context.md

@@ -67,7 +67,7 @@ Constraints that will apply to this project:
   - Observability: Datadog
   ...
 
-Downstream agents will respect these throughout the arc.
+Downstream agents will respect these throughout the project run.
 
 Suggested next: /god-init (or /god-mode if you're ready to build)
 ```

package/skills/god-preflight.md

@@ -1,12 +1,12 @@
 ---
 name: god-preflight
 description: |
-  Run a read-only intake audit before arc-ready, pillars, archaeology, or
+  Run a read-only intake audit before project-run readiness, pillars, archaeology, or
   reconstruction work. Inventory the codebase, surface blockers, and recommend
   the safest next pass without changing project code.
 
   Triggers on: "god preflight", "/god-preflight", "preflight audit",
-  "audit before arc-ready", "audit before pillars", "intake audit"
+  "audit before project-run readiness", "audit before pillars", "intake audit"
 ---
 
 # /god-preflight
@@ -15,7 +15,7 @@ Read-only intake audit for an existing codebase.
 
 ## When to use
 
-- Before applying arc-ready direction to an existing repo
+- Before applying project-run direction to an existing repo
 - Before scoring the repo against pillars
 - Before brownfield archaeology or reconstruction
 - When deciding whether to restructure, refactor, initialize Godpowers, or pause
@@ -28,7 +28,7 @@ It answers:
 
 - What kind of project is this?
 - What structure, tooling, tests, docs, CI, deploy paths, and agent instructions exist?
-- What is missing before arc-ready can make good decisions?
+- What is missing before the project run can make good decisions?
 - Which pillar weaknesses are already visible?
 - What areas are risky to refactor before more evidence exists?
 - What is the safest next pass?
@@ -137,6 +137,20 @@ 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
+
+End the user-facing response with a proposition 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]
+```
+
 ## Guardrails
 
 - Build nothing.

package/skills/god-quick.md

@@ -11,7 +11,7 @@ description: |
 # /god-quick
 
 Run a focused task with TDD and atomic commits, but skip the full planning
-arc.
+workflow.
 
 ## When to use
 

package/skills/god-reconcile.md

@@ -74,7 +74,12 @@ Recommended sequence:
   Main work:  [/god-feature scoped to Milestone 2]
   Post-work:  [/god-sync]
 
-Run? (yes / show alternatives / cancel)
+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]
 ```
 
 ## Difference from /god-roadmap-check

package/skills/god-reconstruct.md

@@ -58,6 +58,14 @@ Suggested next:
   /god-audit       - score the reconstructed artifacts
   /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.
 ```
 
 ## Caveats

package/skills/god-refactor.md

@@ -88,6 +88,29 @@ Behavior: unchanged
 Suggested next: /god-status or continue with /god-feature
 ```
 
+## Proposal Mode
+
+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
+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>
+```
+
+For performance refactors, prefer partial implementation when measurement is
+missing. Example:
+`Implement partial: /god-spike startup timeline to measure load phases before
+refactoring.`
+
 ## Have-Nots
 
 Refactor FAILS if:

package/skills/god-roadmap-check.md

@@ -57,6 +57,16 @@ After god-roadmap-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:
+
+```
+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]
+```
 
 ## When called manually
 

package/skills/god-roadmap-update.md

@@ -16,7 +16,7 @@ Keep ROADMAP.md as a living artifact.
 ## When to use
 
 - After completing a milestone (mark done, gate passed)
-- After adding a feature mid-arc that wasn't on the original roadmap
+- After adding a feature mid-run that wasn't on the original roadmap
 - When priorities shift (move between Now / Next / Later)
 - When a planned milestone is superseded
 

package/skills/god-skip.md

@@ -45,7 +45,7 @@ The reason is required. Skips without reason are rejected.
 ## Mandatory non-skippable steps
 
 These cannot be skipped:
-- The final `/god-sync` at end of arc
+- The final `/god-sync` at the end of the project run
 - `/god-harden` for projects with `public-facing: true` in intent.yaml
 - Standards gates between tiers (use `/god-standards --override` to bypass with reason)
 

package/skills/god-spike.md

@@ -84,6 +84,13 @@ 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.
+
 REMINDER: spike code is throwaway. Do NOT merge to main.
 ```
 

package/skills/god-standards.md

@@ -54,6 +54,13 @@ Verdict: PARTIAL (87%)
 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]
 ```
 
 ## Auto-invocation