godpowers 1.6.8 → 1.6.10

package/agents/god-orchestrator.md

@@ -1,7 +1,7 @@
 ---
 name: god-orchestrator
 description: |
-  The autonomous arc orchestrator. Runs the full Godpowers workflow from idea
+  The autonomous project-run orchestrator. Runs the full Godpowers workflow from idea
   to hardened production. Spawns specialist agents in fresh contexts per tier
   sub-step. Tracks state in .godpowers/PROGRESS.md. Pauses only for legitimate
   human-only decisions.
@@ -13,11 +13,11 @@ tools: Read, Write, Edit, Bash, Grep, Glob, Task
 # God Orchestrator
 
 You are the **Quarterback** of Godpowers. There is exactly one orchestrator,
-and it is you. Nothing sits above you; nothing else owns the arc. Skills
+and it is you. Nothing sits above you; nothing else owns the project run. Skills
 (/god, /god-next, /god-status) are sideline coaches that read the same
 playbook (routing + recipes + state.json) but do not call plays.
 
-You orchestrate the full Godpowers arc. You DO NOT do the heavy lifting yourself.
+You orchestrate the full Godpowers workflow. You DO NOT do the heavy lifting yourself.
 Your job is to spawn the right specialist agent for each sub-step, verify their
 output passes the gate, update PROGRESS.md, and move to the next step.
 
@@ -267,7 +267,7 @@ Programmatic access via `<runtimeRoot>/lib/recipes.js`:
 - `getRecipe(name)` -> lookup specific recipe
 - `getSequence(recipe)` -> the command sequence to execute
 
-Example: user says "I need to add a feature mid-arc". The matchIntent
+Example: user says "I need to add a feature during the current project run". The matchIntent
 function returns the `add-feature-mid-arc-pause` recipe with sequence
 `[/god-pause-work, /god-feature, /god-resume-work]`. Present this sequence
 with the "why" annotations for each step.
@@ -299,7 +299,7 @@ After PRD and before ARCH, branch on UI or product-experience presence:
 
 ## Linkage and Reverse-Sync
 
-Reverse-sync runs incrementally, not just at end-of-arc:
+Reverse-sync runs incrementally, not just at the end of the project run:
 
 - After each Tier 2 build wave commit: spawn `god-updater` in
   reverse-sync mode. Calls `lib/reverse-sync.run(projectRoot)`:
@@ -314,14 +314,14 @@ Reverse-sync runs incrementally, not just at end-of-arc:
   drift detection, REVIEW-REQUIRED.md finalization, AGENTS.md fence
   refresh.
 
-## Mid-Arc DESIGN/PRODUCT Change Detection
+## Mid-Run DESIGN/PRODUCT Change Detection
 
 Before starting each tier, hash-check DESIGN.md and PRODUCT.md against
 last known hash in state.json:
 
 - If changed: spawn `god-design-reviewer` for two-stage gate (spec +
   quality). Three verdicts: PASS / WARN / BLOCK.
-  - BLOCK: append to `.godpowers/design/REJECTED.md`; pause arc;
+  - BLOCK: append to `.godpowers/design/REJECTED.md`; pause the project run;
     surface diff + reason. Critical-finding gate trigger.
   - WARN: continue with warnings logged to events.jsonl.
   - PASS: continue normal propagation pipeline (impact analysis ->
@@ -339,11 +339,11 @@ The critical-finding gate fires on:
 Only Critical security findings always pause, including under --yolo.
 Everything else must first enter the autonomous repair loop below. A failed
 typecheck, lint, check, unit test, generated artifact lint, or have-nots pass is
-not a reason to declare the arc complete. It is work.
+not a reason to declare the project run complete. It is work.
 
 ## Autonomous Repair Loop
 
-Godpowers full-arc means: plan, build, verify, repair, ship, sync. Do not stop
+Godpowers full project run means: plan, build, verify, repair, ship, sync. Do not stop
 at "artifacts generated" when the repo is still red.
 
 When any mechanical verification fails:
@@ -374,7 +374,7 @@ Do this:
 Under `--yolo`, the repair loop auto-runs. It may commit atomic repair commits
 after tests pass. If a git remote exists and the user passed an explicit push
 flag or the project intent says pushing is allowed, push after the green commit
-and then continue the arc. Pushing is not a terminal state.
+and then continue the project run. Pushing is not a terminal state.
 
 ## Shipping Closure Protocol
 
@@ -382,7 +382,7 @@ The shipping tier must not end by listing a broad provider checklist. God Mode
 either ships, creates the automation needed to ship, or pauses on one precise
 external access bundle.
 
-Default behavior: do not pause mid-arc just to ask for a staging URL. If the
+Default behavior: do not pause mid-run just to ask for a staging URL. If the
 user has not explicitly requested deployed staging verification and no live
 target URL is evidenced, complete every local and CI-verifiable shipping gate,
 write the missing deployed-origin item to
@@ -422,7 +422,7 @@ For deploy, observe, harden, and launch:
    `sign off local-only` to finish with deployed verification deferred, or run
    `/god-deploy --stage` later."
 9. Do not say "Suggested next" for a blocked shipping tier. Say either
-   `Arc complete`, `Arc complete with deployed verification deferred`, or
+   `Project run complete`, `Project run complete with deployed verification deferred`, or
    `PAUSE: external access required`, with the exact artifact that lists the
    required bundle.
 
@@ -431,7 +431,7 @@ For deploy, observe, harden, and launch:
 Use this order when external access is missing:
 
 1. If no live target URL is known from explicit evidence, defer the deployed
-   staging origin request unless the user asked to stage now or the arc has
+   staging origin request unless the user asked to stage now or the project run has
    reached final sign-off.
 2. When staging is requested or final sign-off begins, ask for the deployed
    staging origin only.
@@ -592,14 +592,14 @@ ecosystem.
 
 ### Mandatory Final Sync (always, including --yolo)
 
-Before declaring the arc complete, ALWAYS run /god-sync:
+Before declaring the project run complete, ALWAYS run /god-sync:
 
 1. Spawn god-updater in fresh context
 2. Verify final consistency across all 14 artifact categories:
    - All Tier 1-3 artifacts written and pass have-nots
    - Capture artifacts (BACKLOG, SEEDS, TODOS, THREADS) noted as
      "not-yet-created" if absent (graceful, not a failure)
-3. Update SYNC-LOG.md with the arc completion entry
+3. Update SYNC-LOG.md with the project-run completion entry
 4. Update state.json with all final tier statuses
 
 This step runs regardless of flags:
@@ -609,7 +609,7 @@ This step runs regardless of flags:
 - /god-mode --with-hygiene -> sync runs PLUS hygiene check
 
 After sync, re-run the final verification commands. If any are red, return to
-the autonomous repair loop. This ensures every full-arc run leaves the project
+the autonomous repair loop. This ensures every full project run leaves the project
 green and sync'd, not merely documented. The artifact coverage is consistent
 across all 14 categories.
 
@@ -618,7 +618,29 @@ across all 14 categories.
 After Launch completes, write a transition message:
 
 ```
-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>
+
+What changed:
+  1. <highest-signal user-visible change>
+  2. <highest-signal user-visible change>
+
+Validation:
+  + <command>: <result>
+
+Open items:
+  1. <none, or deployed staging deferred, pending review, unstaged files, etc.>
 
 Project is now in steady state. From here, ongoing work uses these workflows:
 
@@ -635,11 +657,42 @@ Periodic hygiene:
   Quality audit:          /god-audit
   Health check:           /god-hygiene (combines audit + deps + docs)
 
-Or describe what you want to do and /god-next will route.
+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
 ```
 
 Update PROGRESS.md status to `steady-state-active`.
 
+For focused brownfield, hotfix, refactor, or build workflows that finish without a
+full greenfield launch, keep the same closeout shape but set `State` to the
+actual result, such as `partial`, `complete with deployed verification
+deferred`, or `complete but unstaged`. Never end with only changed paths and
+validation results.
+
+If the index was intentionally left untouched because the worktree includes
+unrelated or pre-existing changes, say exactly that:
+
+```
+Current status:
+  State: complete but unstaged
+  Worktree: modified files present
+  Index: untouched
+
+Open items:
+  1. Review the diff and stage only the intended files.
+
+Next:
+  Recommended: run /god-status or review the scoped diff before staging.
+  Why: Godpowers avoided sweeping unrelated local changes into the index.
+```
+
 ### Optional Post-Launch Hygiene (--with-hygiene)
 
 If user invoked `/god-mode --with-hygiene` (or `--yolo` includes hygiene by
@@ -657,7 +710,7 @@ If any hygiene pass surfaces issues:
 
 ### --yolo Behavior in Hygiene
 
-`--yolo` skips hygiene by default (it's noise after a successful arc). User
+`--yolo` skips hygiene by default (it is noise after a successful project run). User
 can opt in with `--yolo --with-hygiene`.
 
 If hygiene IS enabled under --yolo:
@@ -687,7 +740,7 @@ Pass `--yolo` to every spawned specialist agent. They will auto-pick the
 default at every pause condition and log the decision to YOLO-DECISIONS.md.
 
 For brownfield and bluefield, run `/god-preflight` automatically before
-archaeology, reconstruction, arc-ready, pillars, or refactor work when
+archaeology, reconstruction, project-run readiness, pillars, or refactor work when
 `.godpowers/preflight/PREFLIGHT.md` is absent. Treat the preflight report as
 the routing baseline. Under `--yolo`, auto-follow the safest recommended next
 route and log the choice to `.godpowers/YOLO-DECISIONS.md`.
@@ -709,7 +762,7 @@ for human resolution when no safe automatic reconcile route exists.
 
 These are the only --yolo carve-outs. All other pauses are auto-resolved with
 the agent's documented default, and all repairable mechanical failures are
-handled by the autonomous repair loop before the arc can be called complete.
+handled by the autonomous repair loop before the project run can be called complete.
 
 ### Pause Format
 
@@ -736,7 +789,12 @@ Show:
 - commands being run and whether they passed or failed
 - scoped file changes
 - final validation summary
-- `Arc complete` or `PAUSE: external access required`
+- final current status from disk, including progress, lifecycle, open items,
+  worktree/index state, and recommended next action
+- plain-language workflow names. Say "project run" or "workflow" instead of
+  unexplained "arc" in visible output
+- PRD and roadmap visibility when those artifacts exist or are expected
+- `Project run complete` or `PAUSE: external access required`
 
 Hide:
 - raw Task input
@@ -1036,10 +1094,10 @@ rewrite-candidate and no concrete existing evidence is removed.
 ### Mode E: Bluefield (auto-detected)
 - No existing code in current dir
 - BUT org-context.yaml found (in current dir, parent, or grandparent)
-- Run full arc with all decisions constrained by org context
+- Run full project run with all decisions constrained by org context
 - Spawn god-org-context-loader first to load constraints
 - Run greenfield simulation audit after org-context, then run
-  god-greenfieldifier so the arc has an approved artifact plan before PRD.
+  god-greenfieldifier so the project run has an approved artifact plan before PRD.
   The plan explains where canonical Godpowers defaults align with, conflict
   with, or are constrained by org standards.
 - All downstream agents (god-stack-selector, god-architect, god-deploy-engineer,

package/agents/god-reconciler.md

@@ -188,7 +188,7 @@ Run this sequence? (yes / show alternatives / cancel)
 ## Missing artifacts (graceful handling)
 
 Not every artifact exists in every project. Tier 1-3 artifacts get created
-during the arc (`/god-mode` produces 10 of them). Capture artifacts
+during the project run (`/god-mode` produces 10 of them). Capture artifacts
 (BACKLOG, SEEDS, TODOS, THREADS) are lazy: they only exist if the user
 has used those commands.
 

package/bin/install.js

@@ -647,7 +647,7 @@ function main() {
     log('');
     log(`\x1b[36mNext steps:\x1b[0m`);
     log(`  1. Open your AI coding tool in any project directory`);
-    log(`  2. Type: \x1b[36m/god-mode\x1b[0m for full autonomous arc`);
+    log(`  2. Type: \x1b[36m/god-mode\x1b[0m for the full autonomous project run`);
     log(`     Or:   \x1b[36m/god-next\x1b[0m to see what to run next`);
     log(`     Or:   \x1b[36m/god-init\x1b[0m to start a new project`);
     log('');

package/hooks/session-start.sh

@@ -52,7 +52,7 @@ if [ -f "$STATE_FILE" ]; then
     jq -r '
       "  project: " + (.project.name // "(unnamed)"),
       "  mode: " + (.mode // "?") + (if ."mode-d-suite" then " (in suite)" else "" end),
-      "  lifecycle: " + (."lifecycle-phase" // "in-arc")
+      "  lifecycle: " + (if (."lifecycle-phase" // "in-arc") == "in-arc" then "in progress" else (."lifecycle-phase" // "in-arc") end)
     ' "$STATE_FILE" 2>/dev/null || head -20 "$STATE_FILE"
   else
     head -20 "$STATE_FILE"
@@ -66,7 +66,7 @@ fi
 cat <<'EOF'
 
 Next step: run /god-next  (it inspects disk state and proposes the next command)
-Or:       /god-mode for the full autonomous arc
+Or:       /god-mode for the full autonomous project run
 Or:       /god-help to see the catalog
 Or:       /god-status for the full project snapshot
 

package/lib/checkpoint.js

@@ -128,6 +128,9 @@ function write(projectRoot, state) {
   const facts = (state.facts || []).slice(0, MAX_FACTS);
   const factsHash = sha256(JSON.stringify(facts));
   const progress = state.progress || null;
+  const lifecycleDisplay = state.lifecycle === 'in-arc'
+    ? 'in progress'
+    : (state.lifecycle || 'in progress');
 
   const fm = [
     '---',
@@ -171,7 +174,7 @@ function write(projectRoot, state) {
     '',
     `- Project: **${state.project || 'unnamed'}**`,
     `- Mode: **${state.mode || '?'}**${state.modeDSuite ? ' (in multi-repo suite)' : ''}`,
-    `- Lifecycle phase: **${state.lifecycle || 'in-arc'}**`,
+    `- Lifecycle phase: **${lifecycleDisplay}**`,
     progressLine,
     `- Current tier: **${state.currentTier || 'tier-0'}** / **${state.currentSubstep || 'orchestration'}**`,
     `- Last action: \`${state.lastAction || 'unknown'}\` by ${state.lastActor || 'unknown'} at ${ts}`,

package/lib/context-writer.js

@@ -98,7 +98,7 @@ function buildCanonicalContent(state, opts = {}) {
   lines.push('- `/god-status` - re-derive state from disk');
   lines.push('- `/god-next` - what to run next, with reason');
   lines.push('- `/god <free text>` - match intent to a recipe');
-  lines.push('- `/god-mode` - run the full autonomous arc');
+  lines.push('- `/god-mode` - run the full autonomous project run');
   lines.push('- `/god-lint` - validate artifacts against have-nots');
   lines.push('- `/god-scan` - rebuild linkage map from code');
   lines.push('- `/god-review-changes` - walk REVIEW-REQUIRED.md');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "1.6.8",
+  "version": "1.6.10",
   "description": "AI-powered development system: 106 slash commands and 39 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
   "bin": {
     "godpowers": "./bin/install.js"

package/references/HAVE-NOTS.md

@@ -454,7 +454,7 @@ Trust boundaries declared in docs but absent in code. Fail.
 
 ## Workflow-Specific Have-Nots
 
-These apply to artifacts produced by non-arc workflows (postmortem, spike,
+These apply to artifacts produced by focused workflows (postmortem, spike,
 migration, docs, deps).
 
 ### Postmortem Have-Nots

package/references/orchestration/SCALE-DETECTION.md

@@ -8,7 +8,7 @@
 |-------|---------|---------------------|
 | Trivial | Single-file change, bug fix, config tweak | /god-fast (skip planning) |
 | Small | One feature, one service, <1 week | /god-quick OR lightweight /god-mode |
-| Medium | Multiple features, 1-3 services, 1-4 weeks | /god-mode (full arc) |
+| Medium | Multiple features, 1-3 services, 1-4 weeks | /god-mode (full project run) |
 | Large | Multiple services, team coordination, 1-3 months | /god-mode + /god-sprint (sprints) |
 | Enterprise | Multiple teams, compliance, 3+ months | /god-mode + extension packs (security, etc.) |
 

package/references/shared/GLOSSARY.md

@@ -5,7 +5,7 @@
 
 ## Core abstractions
 
-**Tier**: a phase of the dev arc (0: Orchestration, 1: Planning, 2: Building, 3: Shipping).
+**Tier**: a phase of the development workflow (0: Orchestration, 1: Planning, 2: Building, 3: Shipping).
 
 **Sub-step**: a bounded unit within a tier (PRD, ARCH, Roadmap, Stack, Repo, Build, Deploy, Observe, Launch, Harden).
 

package/references/shared/ORCHESTRATORS.md

@@ -69,7 +69,7 @@ frontmatter. There's no proprietary binary state. To leave:
 ## What Godpowers does not try to be
 
 Godpowers is opinionated about: artifact discipline, bidirectional
-linkage, the four-tier arc, the single-orchestrator rule, headless
+linkage, the four-tier workflow, the single-orchestrator rule, headless
 runtime verification, and the substitution / three-label / have-nots
 gates. It is intentionally not opinionated about: team ceremonies,
 sprint cadence, ticket trackers, knowledge graphs, prompt engineering

package/routing/god-mode.yaml

@@ -2,7 +2,7 @@ apiVersion: godpowers/v1
 kind: CommandRouting
 metadata:
   command: /god-mode
-  description: Full autonomous arc
+  description: Full autonomous project run
   tier: 0
 
 prerequisites:

package/routing/god-preflight.yaml

@@ -2,7 +2,7 @@ apiVersion: godpowers/v1
 kind: CommandRouting
 metadata:
   command: /god-preflight
-  description: Read-only intake audit before arc-ready and pillars
+  description: Read-only intake audit before project-run readiness and pillars
   tier: 0
 
 prerequisites:

package/routing/recipes/add-feature-mid-arc-pause.yaml

@@ -3,7 +3,7 @@ kind: Recipe
 metadata:
   name: add-feature-mid-arc-pause
   category: feature-addition
-  description: "Bigger feature mid-arc; reconcile with roadmap, pause arc, do feature, update roadmap, resume"
+  description: "Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume"
 
 triggers:
   intent-keywords:
@@ -16,18 +16,18 @@ triggers:
 
 sequences:
   default:
-    description: "Bigger feature mid-arc; reconcile with roadmap, pause arc, do feature, update roadmap, resume"
+    description: "Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume"
     steps:
       - command: "/god-reconcile"
         why: "Multi-artifact reconciliation across PRD/ARCH/ROADMAP/STACK/etc."
       - command: "/god-pause-work"
-        why: "Save current arc state"
+        why: "Save current project-run state"
         skip-when: reconciliation-says-already-done-or-prereq
       - command: "/god-feature"
         why: "Run feature workflow with full discipline"
       - command: "/god-sync"
         why: "Update all affected artifacts (PRD, ARCH, ROADMAP, etc.)"
       - command: "/god-resume-work"
-        why: "Restore arc state"
+        why: "Restore project-run state"
 
 default-sequence: default

package/routing/recipes/bluefield-org-aware.yaml

@@ -20,7 +20,7 @@ sequences:
       - command: "/god-org-context init"
         why: "Capture org-level standards and constraints"
       - command: "/god-preflight"
-        why: "Inspect inherited context before arc-ready and pillars"
+        why: "Inspect inherited context before project-run readiness and pillars"
       - command: "/god-init"
         why: "Detect bluefield mode"
       - command: "/god-mode --bluefield"

package/routing/recipes/brownfield-onboarding.yaml

@@ -19,7 +19,7 @@ sequences:
     description: "Inheriting an existing codebase; preflight before archaeology"
     steps:
       - command: "/god-preflight"
-        why: "Read-only intake audit before arc-ready and pillars"
+        why: "Read-only intake audit before project-run readiness and pillars"
       - command: "/god-archaeology"
         why: "Deep history, decisions, conventions, risks"
       - command: "/god-reconstruct"

package/routing/recipes/greenfield-fast.yaml

@@ -20,6 +20,6 @@ sequences:
     description: "Greenfield idea to production with one command"
     steps:
       - command: "/god-mode"
-        why: "Full autonomous arc, idea to hardened production"
+        why: "Full autonomous project run, idea to hardened production"
 
 default-sequence: default

package/routing/recipes/greenfield-with-ideation.yaml

@@ -24,6 +24,6 @@ sequences:
       - command: "/god-init"
         why: "Commit to clarified framing"
       - command: "/god-mode"
-        why: "Run autonomous arc"
+        why: "Run autonomous project run"
 
 default-sequence: default

package/skills/god-agent-audit.md

@@ -62,6 +62,13 @@ Warnings:
 
 Infos: 90 missing-recommended-section suggestions across agents
        (run with --json for full list)
+
+Proposition:
+  1. Implement partial: fix the highest-priority error or warning
+  2. Implement complete: /god-agent-audit --fix for info-level placeholder sections only
+  3. Discuss more: /god-discuss agent contract findings
+  4. Inspect details: /god-agent-audit --json
+Recommended: [one option and why]
 ```
 
 ## Backward-compatibility promise

package/skills/god-archaeology.md

@@ -45,4 +45,11 @@ Suggested next:
   /god-reconstruct  - reverse-engineer planning artifacts from this code
   /god-tech-debt    - assess and prioritize debt revealed
   /god-feature      - now safe to add new work with archaeology in hand
+
+Proposition:
+  1. Implement partial: /god-tech-debt for only the highest-risk areas
+  2. Implement complete: /god-reconstruct then /god-audit for full brownfield alignment
+  3. Discuss more: /god-discuss the open tribal-knowledge questions
+  4. Run God Mode: /god-mode only after reconstruction or audit makes the state clear
+Recommended: /god-reconstruct when planning artifacts are missing or stale.
 ```

package/skills/god-audit.md

@@ -23,7 +23,7 @@ Spawn the **god-auditor** agent in a fresh context via Task tool.
 When invoked by `brownfield-arc` or `bluefield-arc` with
 `mode: greenfield-simulation`, spawn god-auditor with the current project
 evidence and ask it to compare the repo or org constraints against the
-canonical Godpowers greenfield arc. The agent writes
+canonical Godpowers greenfield project run. The agent writes
 `.godpowers/audit/GREENFIELD-SIMULATION.md`.
 
 This mode builds nothing and rewrites no planning artifacts. It exists so
@@ -52,6 +52,16 @@ After god-auditor returns:
 1. Verify AUDIT-REPORT.md exists on disk
 2. Display the summary table to the user
 3. If any artifact scored below 80%: suggest re-running the failing tier
+4. End with a proposition block:
+
+```
+Proposition:
+  1. Implement partial: [rerun the single lowest-scoring tier or fix the top finding]
+  2. Implement complete: [rerun all failing tiers in priority order]
+  3. Discuss more: /god-discuss audit remediation plan
+  4. Run God Mode: /god-mode only when the audit has no blocking findings
+Recommended: [one option and why]
+```
 
 ## Output Format
 

package/skills/god-context-scan.md

@@ -89,6 +89,19 @@ Suggested next:
 2. Accept the 2 new todos: /god-check-todos
 ```
 
+## Proposition Closeout
+
+End every context scan report with a proposition block:
+
+```
+Proposition:
+  1. Implement partial: [first suggested action, usually /god-locate or /god-repair]
+  2. Implement complete: resolve all error and warn drifts, then rerun /god-context-scan
+  3. Discuss more: /god-discuss context drift
+  4. Inspect status: /god-status after re-orientation
+Recommended: [one option and why]
+```
+
 ## What this does NOT do
 
 - Does not modify state. Read-only.

package/skills/god-context.md

@@ -132,7 +132,7 @@ Done. AI tools will no longer see Godpowers context on this project.
 
 ## Auto-refresh
 
-When `/god-sync` runs (post-arc, or any sync), `god-updater` calls this skill
+When `/god-sync` runs (after a project run, or any sync), `god-updater` calls this skill
 with `refresh` to keep `AGENTS.md` content aligned with the latest project
 state (mode, scale, completed tiers, active artifacts).
 

package/skills/god-deploy.md

@@ -50,7 +50,7 @@ required, record the single access bundle in
 requests staging or final sign-off begins.
 
 The single access bundle must be incremental. Do not ask for
-`STAGING_APP_URL` mid-arc unless the user requested deployed staging. At final
+`STAGING_APP_URL` mid-run unless the user requested deployed staging. At final
 sign-off or explicit staging, ask for the smallest next item needed to run the
 next command. If no live target URL is known, ask only for
 `STAGING_APP_URL=<staging-origin>` and the exact smoke command that will run.

package/skills/god-design-impact.md

@@ -65,6 +65,14 @@ Transitive (depth 2):
 
 Recommendation: Run /god-design with this change to apply.
 god-design-reviewer will gate via two-stage review.
+
+Proposition:
+  1. Implement partial: /god-design for only the lowest-risk token or component change
+  2. Implement complete: /god-design with the full proposed change
+  3. Discuss more: /god-discuss the design tradeoff before changing files
+  4. Run God Mode: /god-mode only if this design change is part of a wider project run
+Recommended: apply the smallest design change first when severity is warning
+or higher.
 ```
 
 ## When this skill helps

package/skills/god-discuss.md

@@ -67,4 +67,11 @@ Key findings:
   - [term or ambiguity resolved]
 
 Suggested next: [the planning command this discussion was for]
+
+Proposition:
+  1. Implement partial: [smallest safe slice or planning command]
+  2. Implement complete: [full command that consumes this brief]
+  3. Discuss more: /god-discuss [specific unresolved question]
+  4. Run God Mode: /god-mode [scope] if the user wants autonomous execution
+Recommended: [one option and why]
 ```

package/skills/god-doctor.md

@@ -65,6 +65,23 @@ Suggested next steps:
   2. /god-restore  (review trash)
 ```
 
+## Proposition Closeout
+
+End every human-readable doctor report with a proposition block:
+
+```
+Proposition:
+  1. Implement partial: [safest single fix or diagnostic follow-up]
+  2. Implement complete: /god-doctor --fix when all proposed fixes are safe categories
+  3. Discuss more: /god-discuss [highest-risk warning or unclear repair]
+  4. Inspect status: /god-status after repair
+Recommended: [one option and why it is safe]
+```
+
+If the report contains errors that need manual repair, do not recommend
+`/god-doctor --fix` as complete. Recommend the highest-priority manual repair
+or `/god-repair` instead.
+
 ## Subcommands
 
 ### `/god-doctor`

package/skills/god-explore.md

@@ -47,4 +47,12 @@ Idea explored. Suggested framing:
 
 Suggested next: /god-init (commit to this framing) or /god-explore again
                 (if you want to try another angle)
+
+Proposition:
+  1. Implement partial: /god-init with this framing and stop after PRD
+  2. Implement complete: /god-mode with this framing for the full project run
+  3. Discuss more: /god-explore again with the weakest assumption
+  4. Run God Mode: /god-mode if the user is ready to build now
+Recommended: /god-init when the framing feels stable enough to turn into
+requirements.
 ```

package/skills/god-extract-learnings.md

@@ -15,7 +15,7 @@ Capture institutional knowledge from a completed phase or milestone.
 ## When to use
 
 - After completing a milestone (Now -> Done)
-- After a successful /god-mode arc
+- After a successful /god-mode project run
 - Before a /god-postmortem (different focus: that's for incidents)
 
 ## Process

package/skills/god-feature.md

@@ -1,7 +1,7 @@
 ---
 name: god-feature
 description: |
-  Add a feature to an existing project. Skips the full-arc setup (no /god-init,
+  Add a feature to an existing project. Skips the full project-run setup (no /god-init,
   no repo scaffolding, no /god-stack). Mini-PRD for the feature, optional
   micro-architecture, build, deploy via existing pipeline, harden new code.