godpowers 1.6.9 → 1.6.10

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?
@@ -147,7 +147,7 @@ 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 arc-ready or the remaining gaps are acceptable
+  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]
 ```
 

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

@@ -102,7 +102,7 @@ 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 arc
+  4. Run God Mode: /god-mode <scope> if the user wants the full autonomous project run
 Recommended: <one option and why>
 ```
 

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

@@ -88,7 +88,7 @@ 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 arc
+  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-status.md

@@ -34,6 +34,8 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
 6. Report:
    - Current mode and scale
    - Progress summary: percentage, completed step count, current step number
+   - Planning visibility: PRD status, roadmap status, active milestone, and
+     completion basis
    - What happened recently, using CHECKPOINT.md actions when available
    - What happens next, using routing and disk state
    - Per-tier status (with disk verification)
@@ -51,6 +53,12 @@ Started: 2026-05-09
 Progress: 15% (2 of 13 steps complete; current step 3 of 13)
 Current: Tier 1 Planning / Architecture
 
+Planning visibility:
+  PRD: done .godpowers/prd/PRD.md
+  Roadmap: pending
+  Current milestone: Planning / Architecture
+  Completion: 15% based on PROGRESS.md tracked steps
+
 What happened recently:
   1. PRD artifact verified on disk
   2. Tier state refreshed from state.json
@@ -100,7 +108,7 @@ how much momentum to give Godpowers:
 ```
 Proposition:
   1. Implement partial: [single next command from "What happens next"]
-  2. Implement complete: /god-mode to continue the current arc when no blockers are present
+  2. Implement complete: /god-mode to continue the current project run when no blockers are present
   3. Discuss more: /god-discuss [unclear state, blocker, or inconsistency]
   4. Inspect status: /god-locate or /god-next for a smaller routing view
 Recommended: [one option and why it fits the disk-derived state]

package/skills/god-suite-init.md

@@ -81,6 +81,6 @@ shared-standards:
 ## What this does NOT do
 
 - Modify any repo's source code
-- Run an arc on any repo
+- Run a project run on any repo
 - Override existing per-repo state.json beyond adding the
   `suite.hubPath` pointer

package/skills/god-suite-release.md

@@ -33,7 +33,7 @@ A version bump that knows about dependents. Different from `/god-launch`
    - Scans suite version-table for repos that depend on the bumped repo
    - For each dependent: writes a per-repo orchestrator handoff file and
      spawns its `god-orchestrator` with only a display-safe pointer for the
-     `version-bump` directive (NOT a full arc)
+     `version-bump` directive (NOT a full project run)
    - Aggregates results per-repo
    - Updates `.godpowers/suite-config.yaml` version-table to match
    - Appends to `.godpowers/suite/SYNC-LOG.md`

package/skills/god-suite-status.md

@@ -39,7 +39,7 @@ Aggregate
 Per-repo
 | Repo      | Mode | Phase     | Artifacts | Coverage | Drift | Reviews |
 |-----------|------|-----------|-----------|----------|-------|---------|
-| dashboard | A    | in-arc    | 12        | 92%      | 0     | 1       |
+| dashboard | A    | in progress | 12        | 92%      | 0     | 1       |
 | api       | A    | steady    | 18        | 85%      | 2     | 2       |
 | docs      | A    | steady    | 12        | 84%      | 1     | 2       |
 

package/skills/god-suite-sync.md

@@ -46,4 +46,4 @@ warnings by default; surfaces in REVIEW-REQUIRED.md per repo.
 - Touch files NOT declared in `byte-identical:` of suite-config.yaml
 - Modify per-repo state.json (only the syncer agent writes; no
   Quarterback-level changes)
-- Run any arc inside a sibling repo
+- Run any project run inside a sibling repo

package/skills/god-tech-debt.md

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

package/skills/god.md

@@ -28,7 +28,7 @@ Before calling runtime modules, resolve the Godpowers runtime root:
 
 Slash commands are precise but require the user to know the command name.
 Recipes are scenario-shaped ("I'm coming back after a week", "production is
-broken", "add a feature mid-arc") and match free-text intent. `/god` is the
+broken", "add a feature during the current project run") and match free-text intent. `/god` is the
 front door that turns intent into the right slash command.
 
 This skill complements `/god-next` rather than replacing it:
@@ -39,7 +39,7 @@ This skill complements `/god-next` rather than replacing it:
 | `/god-next` | "I just finished X, what's next?" or pre-flight checks |
 | `/god-status` | "Where are we? what's done?" |
 | `/god-init` | "Start a project here" |
-| `/god-mode` | "Run the whole arc autonomously" |
+| `/god-mode` | "Run the whole project run autonomously" |
 
 ## Process
 
@@ -48,8 +48,8 @@ This skill complements `/god-next` rather than replacing it:
 Treat everything after `/god` as free text. If empty, treat as state-driven.
 
 ```
-/god add a feature without breaking the current arc
-   text = "add a feature without breaking the current arc"
+/god add a feature without breaking the current project run
+   text = "add a feature without breaking the current project run"
 
 /god
    text = "" -> state-driven mode
@@ -120,7 +120,7 @@ Proposition:
   1. Implement partial: <smallest safe command or slice>
   2. Implement complete: <full command sequence>
   3. Discuss more: /god-discuss <topic or unresolved question>
-  4. Run God Mode: /god-mode <scope> if the user wants the full autonomous arc
+  4. Run God Mode: /god-mode <scope> if the user wants the full autonomous project run
 Recommended: <one option and why>
 ```
 
@@ -178,8 +178,8 @@ User: /god add a new feature
 
 Top matches for "add a new feature":
 
-  1. add-feature-mid-arc-pause       (15)   Pause /god-mode arc, run feature, resume
-  2. add-feature-small               (10)   Lightweight feature, no arc context
+  1. add-feature-mid-arc-pause       (15)   Pause /god-mode, run feature, resume
+  2. add-feature-small               (10)   Lightweight feature, no project-run context
   3. add-feature-next-milestone      (10)   Defer to next milestone
 
 Pick one (1/2/3) or describe more specifically.
@@ -210,7 +210,7 @@ User: /god make me a sandwich
 No recipe matched. Falling back to state-driven suggestion.
 
 Where you are: tier-3 launched
-Structural next: (none, arc complete)
+Structural next: (none, project run complete)
 
 Suggested: /god-next   show all valid next-step options
        or: /god-status   re-derive state from disk

package/workflows/bluefield-arc.yaml

@@ -12,7 +12,7 @@ metadata:
     Bluefield: new code, existing org context. Loads org standards first,
     runs a preflight intake against the surrounding environment, runs a
     greenfield simulation audit against those constraints, then runs a
-    user-approved greenfieldification pass before the full arc.
+    user-approved greenfieldification pass before the full project run.
 
 on: [/god-bluefield, /god-mode --bluefield]
 

package/workflows/brownfield-arc.yaml

@@ -11,7 +11,7 @@ metadata:
   description: |
     Brownfield: existing codebase, inspect before prescribing. Preflight +
     archaeology + reconstruction + debt assessment + greenfield simulation
-    audit, then a user-approved greenfieldification pass before normal arc
+    audit, then a user-approved greenfieldification pass before normal project-run
     workflows.
 
 on: [/god-brownfield, /god-mode --brownfield]

package/workflows/feature-arc.yaml

@@ -9,7 +9,7 @@ metadata:
   name: feature-arc
   version: 1.0.0
   description: |
-    Add a feature to an existing project. Skips full-arc setup.
+    Add a feature to an existing project. Skips full project-run setup.
     Run by /god-feature.
 
 on: [/god-feature]