godpowers 1.6.9 → 1.6.10

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.9",
+  "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-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

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

@@ -70,7 +70,7 @@ 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 arc
+  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.
 ```

package/skills/god-explore.md

@@ -50,7 +50,7 @@ Suggested next: /god-init (commit to this framing) or /god-explore again
 
 Proposition:
   1. Implement partial: /god-init with this framing and stop after PRD
-  2. Implement complete: /god-mode with this framing for the full arc
+  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

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.
 

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
 

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]
@@ -119,7 +122,7 @@ 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 arc
+  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]

package/skills/god-locate.md

@@ -80,7 +80,7 @@ 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 arc when no drift is flagged
+  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]

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-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
 

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)
 ```