godpowers 0.15.0

package/skills/god-suite-init.md

@@ -0,0 +1,75 @@
+---
+name: god-suite-init
+description: |
+  Register a multi-repo suite (Mode D). Prompts for siblings,
+  byte-identical files, version table, and shared standards; writes
+  `.godpowers/suite-config.yaml` to the hub; updates each sibling's
+  state.json to point at the hub.
+
+  Triggers on: "god suite init", "/god-suite-init", "register multi-repo",
+  "set up suite", "mode d"
+---
+
+# /god-suite-init
+
+One-time registration for a multi-repo workspace. Per the locked
+answer to plan question Q1: explicit declaration only. Sibling repos
+are listed manually; godpowers does NOT auto-walk parent dirs.
+
+## Forms
+
+| Form | Action |
+|---|---|
+| `/god-suite-init` | Interactive setup; prompts for all fields |
+| `/god-suite-init --hub <path>` | Use a specific dir as the hub |
+
+## Process
+
+1. Verify the working dir is intended as the hub (or `--hub` resolves to one).
+2. Prompt for:
+   - Suite name
+   - Sibling repo paths (one per line, relative or absolute)
+   - Byte-identical files to track (one per line; e.g., LICENSE, .editorconfig)
+   - Version-table entries (optional; can be added later)
+   - Shared standards (node-version, linter; optional)
+3. Spawn `god-coordinator` agent in `init` mode with collected inputs.
+4. god-coordinator writes `.godpowers/suite-config.yaml` and updates
+   each sibling's state.json with `suite.hubPath`.
+5. Initial `lib/suite-state.refreshFromRepos` runs to populate
+   `.godpowers/suite/state.json` and `STATE.md`.
+6. Report registration complete; suggest `/god-suite-status` next.
+
+## Output
+
+- `.godpowers/suite-config.yaml` (hub)
+- `.godpowers/suite/state.json` (hub; aggregate)
+- `.godpowers/suite/STATE.md` (hub; human-readable)
+- Updates to each sibling's `state.json` (`suite.hubPath` field)
+
+## Suite-config schema
+
+```yaml
+name: my-suite
+siblings:
+  - repo-a
+  - repo-b
+  - { name: external-repo, path: ../external-repo }
+byte-identical:
+  - .editorconfig
+  - LICENSE
+  - .github/workflows/ci.yml
+version-table:
+  shared-libs:
+    repo-a: 1.2.3
+    repo-b: 1.2.3
+shared-standards:
+  node-version: 20
+  linter: biome
+```
+
+## What this does NOT do
+
+- Modify any repo's source code
+- Run an arc on any repo
+- Override existing per-repo state.json beyond adding the
+  `suite.hubPath` pointer

package/skills/god-suite-patch.md

@@ -0,0 +1,64 @@
+---
+name: god-suite-patch
+description: |
+  Coordinated change touching multiple repos in a Mode D suite. One
+  logical change; multiple PRs, atomically tracked. Use for refactors
+  spanning shared code + dependents.
+
+  Triggers on: "god suite patch", "/god-suite-patch",
+  "coordinated patch", "cross-repo refactor"
+---
+
+# /god-suite-patch
+
+A single change description applied across multiple repos in the
+suite. Each affected repo's `god-orchestrator` runs the patch
+locally; the coordinator tracks atomicity.
+
+## Process
+
+1. Verify suite is registered.
+2. Prompt for:
+   - Patch description (what's the change)
+   - Repos in scope (defaults: all siblings; user can subset)
+   - Per-repo any specific notes
+3. Spawn `god-coordinator` in `patch` mode.
+4. For each repo in scope:
+   - Spawn that repo's `god-orchestrator` with the patch directive
+   - Track success/failure
+5. Coordinator aggregates results:
+   - All succeeded: report success; append to SYNC-LOG.md
+   - Some failed: report partial; suggest manual continuation OR
+     rollback (`/god-suite-patch --rollback <patch-id>`)
+
+## Forms
+
+| Form | Action |
+|---|---|
+| `/god-suite-patch "<description>"` | Apply across all siblings |
+| `/god-suite-patch "<description>" --repos a,b` | Subset |
+| `/god-suite-patch --dry-run` | Show what would change per repo |
+| `/god-suite-patch --rollback <id>` | Undo a previous suite-patch |
+
+## Atomicity
+
+Per-repo orchestrators run independently. If one fails:
+- The coordinator does NOT auto-rollback the others
+- It reports the failure and asks the user
+- Rollback is opt-in via `--rollback`
+
+This matches the Quarterback rule: each repo's orchestrator owns its
+own state. Cross-repo atomicity is human-coordinated, not magic.
+
+## Use cases
+
+- "Rename X to Y everywhere it appears"
+- "Update all repos to use the new shared-libs API"
+- "Fix CVE-2026-XXXX across all services that use vulnerable lib"
+- "Add a new shared CI step to all repos"
+
+## What this does NOT do
+
+- Bypass per-repo lint, design-review, or runtime gates
+- Apply changes to repos that aren't declared siblings
+- Auto-rollback (preserved as explicit user action)

package/skills/god-suite-release.md

@@ -0,0 +1,58 @@
+---
+name: god-suite-release
+description: |
+  Coordinate a release across siblings in a Mode D suite. When repo A
+  bumps version, scan all dependents for impact and propagate updates.
+
+  Triggers on: "god suite release", "/god-suite-release",
+  "coordinated release", "bump and propagate"
+---
+
+# /god-suite-release
+
+A version bump that knows about dependents. Different from `/god-launch`
+(per-repo); this coordinates ACROSS repos.
+
+## Process
+
+1. Verify suite is registered.
+2. Prompt for: which repo, new version, release notes.
+3. Spawn `god-coordinator` in `release` mode.
+4. god-coordinator:
+   - Scans suite version-table for repos that depend on the bumped repo
+   - For each dependent: spawns its `god-orchestrator` with a
+     `version-bump` directive (NOT a full arc)
+   - Aggregates results per-repo
+   - Updates `.godpowers/suite-config.yaml` version-table to match
+   - Appends to `.godpowers/suite/SYNC-LOG.md`
+5. Reports aggregated outcome (bumped + propagated repos).
+
+## Forms
+
+| Form | Action |
+|---|---|
+| `/god-suite-release <repo> <version>` | Bump and propagate |
+| `/god-suite-release <repo> <version> --dry-run` | Show impact; no changes |
+| `/god-suite-release <repo> <version> --no-propagate` | Bump only the named repo |
+
+## What this does
+
+- Updates the bumped repo's version (via its orchestrator)
+- For each dependent: updates its package.json declared version
+- Updates suite-config.yaml version-table
+- Appends release entry to SYNC-LOG.md
+- Triggers per-repo `/god-launch` (or equivalent) only when the user
+  explicitly confirms each launch
+
+## What this does NOT do
+
+- Auto-launch all dependents (each repo's launch gate still runs;
+  user confirms)
+- Bypass per-repo critical-finding gates
+- Modify code beyond what version bumps require
+
+## Quarterback rule preserved
+
+Each repo's `god-orchestrator` retains full control over its own
+release. The coordinator orchestrates the cross-repo coordination
+without bypassing per-repo gates.

package/skills/god-suite-status.md

@@ -0,0 +1,63 @@
+---
+name: god-suite-status
+description: |
+  Show all repos' status side-by-side in a Mode D suite. Refreshes
+  per-repo state, runs meta-linter, displays aggregate metrics.
+
+  Triggers on: "god suite status", "/god-suite-status", "suite status",
+  "all repos status"
+---
+
+# /god-suite-status
+
+The `/god-status` equivalent for the whole suite. Refreshes each
+repo's state, runs cross-repo invariants, prints a single aggregated
+report.
+
+## Process
+
+1. Verify `.godpowers/suite-config.yaml` exists (or sibling's
+   state.json points at a hub).
+2. Spawn `god-coordinator` in `status` mode.
+3. god-coordinator runs:
+   - `lib/suite-state.refreshFromRepos(hubPath)` to aggregate state
+   - `lib/meta-linter.runAll(hubPath)` to check invariants
+   - `lib/cross-repo-linkage.collectAllIds(hubPath)` to count IDs
+4. Prints the formatted report.
+
+## Output (example)
+
+```
+Suite: my-products
+
+Aggregate
+  Total artifacts complete: 42
+  Total drift findings: 3
+  Pending reviews: 5
+  Average linkage coverage: 87%
+
+Per-repo
+| Repo      | Mode | Phase     | Artifacts | Coverage | Drift | Reviews |
+|-----------|------|-----------|-----------|----------|-------|---------|
+| dashboard | A    | in-arc    | 12        | 92%      | 0     | 1       |
+| api       | A    | steady    | 18        | 85%      | 2     | 2       |
+| docs      | A    | steady    | 12        | 84%      | 1     | 2       |
+
+Meta-lint findings (3):
+  [WARNING] byte-identical-drift: .editorconfig differs across repos
+  [WARNING] version-table-drift: api 2.4 declared, package.json has 2.3
+  [WARNING] shared-standard-drift: docs uses eslint, suite declares biome
+
+Suggested next:
+  /god-suite-sync   to address byte-identical drift
+  /god-review-changes  in dashboard repo (1 pending)
+  /god-review-changes  in api repo (2 pending)
+```
+
+## Forms
+
+| Form | Action |
+|---|---|
+| `/god-suite-status` | Default report |
+| `/god-suite-status --json` | Structured JSON |
+| `/god-suite-status --strict` | Promote warnings to errors (per Q2 lock) |

package/skills/god-suite-sync.md

@@ -0,0 +1,49 @@
+---
+name: god-suite-sync
+description: |
+  Propagate byte-identical files across all repos in a Mode D suite.
+  Detects drift via meta-linter; user picks canonical version; copies
+  to all siblings.
+
+  Triggers on: "god suite sync", "/god-suite-sync", "sync byte-identical",
+  "propagate config", "fix .editorconfig drift"
+---
+
+# /god-suite-sync
+
+Resolve byte-identical drift across siblings. Per locked Q2: drift is
+warnings by default; surfaces in REVIEW-REQUIRED.md per repo.
+`--strict` upgrades to hard gate.
+
+## Process
+
+1. Spawn `god-coordinator` in `sync` mode.
+2. god-coordinator runs `lib/meta-linter.checkByteIdentical(hubPath)`.
+3. For each drifted file:
+   - Print the diff between siblings (showing hashes + first-line preview)
+   - Ask user: which version is canonical?
+   - On answer: copy canonical content to all other siblings
+4. After all drifted files resolved: append entry to
+   `.godpowers/suite/SYNC-LOG.md`
+5. Refresh suite state.
+
+## Forms
+
+| Form | Action |
+|---|---|
+| `/god-suite-sync` | Interactive: prompt per drifted file |
+| `/god-suite-sync --canonical <repo>` | Auto-apply: use this repo's version everywhere |
+| `/god-suite-sync --dry-run` | Show what would change; no writes |
+
+## Output
+
+- Modified byte-identical files in non-canonical repos
+- Append entry to `.godpowers/suite/SYNC-LOG.md`
+- Refreshed `.godpowers/suite/state.json`
+
+## What this does NOT do
+
+- 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

package/skills/god-sync.md

@@ -0,0 +1,102 @@
+---
+name: god-sync
+description: |
+  Sync all affected artifacts after feature work. Updates PRD, ARCH, ROADMAP,
+  STACK, DEPLOY, OBSERVE, HARDEN, LAUNCH, BACKLOG, SEEDS, TODOS, THREADS
+  based on what the work actually touched. Closes the loop after
+  /god-reconcile + feature execution.
+
+  Triggers on: "god sync", "/god-sync", "sync everything", "update all",
+  "close the loop", "post-work sync"
+---
+
+# /god-sync
+
+Update all artifacts after feature work.
+
+## When auto-invoked
+
+End of feature-addition recipes. After feature work completes, /god-sync
+runs to ensure no artifact drifts.
+
+## When manually invoked
+
+User runs `/god-sync` after manual changes. Useful for:
+- After making code changes outside the recipe flow
+- Periodic sync to catch drift
+- Before declaring a milestone complete
+
+## Setup
+
+1. Verify `.godpowers/` exists
+2. Spawn god-updater in fresh context with:
+   - The reconciliation verdict (if available from a prior /god-reconcile)
+   - Or: re-run reconciliation against current state to detect what changed
+   - Recent commits for context
+
+## Verification
+
+After god-updater returns:
+1. Verify each touched artifact passes its tier's have-nots
+2. Verify SYNC-LOG.md was appended
+3. Verify state.json reflects new tier statuses
+4. Display summary of what changed
+
+## Output
+
+```
+Sync complete.
+
+Updated:
+  - prd/PRD.md (added requirement P-MUST-12)
+  - arch/ARCH.md (added ADR-007)
+  - roadmap/ROADMAP.md (Milestone 2 marked complete)
+  - deploy/STATE.md (new env var)
+  - observe/STATE.md (new SLO)
+  - backlog/BACKLOG.md (entry resolved)
+  - todos/TODOS.md (1 todo marked done)
+  - threads/auth-migration.md (progress note)
+
+Have-nots: all passing
+SYNC-LOG.md updated.
+
+Suggested next: /god-status
+```
+
+## What this prevents
+
+| Drift type | How /god-sync catches it |
+|---|---|
+| Roadmap drift | Marks milestones complete; appends new entries |
+| PRD-roadmap divergence | Flags if roadmap added work not in PRD |
+| Stale ARCH | Adds ADR for new architectural decisions |
+| Forgotten SLOs | New endpoints/features get SLO entries |
+| Backlog cruft | Resolved entries linked to commits |
+| Orphan todos | Closes superseded todos |
+| Lost threads | Active threads get progress notes |
+
+The loop:
+
+```
+  /god-reconcile  ->  recipe execution  ->  /god-sync
+      (before)         (the actual work)       (after)
+```
+
+Both bookends run automatically in feature-addition recipes. Both can be
+invoked manually for spot-checks.
+
+
+## Locking
+
+The orchestrator acquires a state-lock before this skill mutates anything,
+scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
+`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
+same holder; force-reclaimable if stale via `/god-repair`.
+
+Read-only inspection commands (`/god-status`, `/god-doctor`,
+`/god-locate`) do NOT block on the lock. Concurrent writers on
+non-overlapping scopes are allowed; on overlapping scopes, the second
+writer pauses or routes elsewhere via `/god-next`.
+
+See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
+the full contract.

package/skills/god-tech-debt.md

@@ -0,0 +1,56 @@
+---
+name: god-tech-debt
+description: |
+  Assess and prioritize technical debt across 8 categories: code, design,
+  dependency, security, test, doc, operational, knowledge. Outputs P0-P3
+  prioritized remediation plan with cost/impact estimates.
+
+  Triggers on: "god tech debt", "/god-tech-debt", "tech debt assessment",
+  "debt audit", "prioritize debt"
+---
+
+# /god-tech-debt
+
+Categorize, prioritize, plan tech debt remediation.
+
+## When to use
+
+- Quarterly health check on a brownfield project
+- Before /god-upgrade or /god-refactor on legacy code
+- After /god-archaeology surfaced concerns
+- Before promising features that may need debt paydown first
+
+## Setup
+
+1. Verify codebase exists
+2. Spawn god-debt-assessor in fresh context
+
+## Verification
+
+- `.godpowers/tech-debt/REPORT.md` exists
+- All 8 debt categories assessed (no silent skips)
+- Items prioritized P0/P1/P2/P3 with cost + impact rationale
+- P0 items have specific recommended commands
+
+## On Completion
+
+```
+Tech debt assessment complete: .godpowers/tech-debt/REPORT.md
+
+Summary:
+  P0 (do this sprint):    [N] items, [N] person-weeks
+  P1 (this quarter):      [N] items
+  P2 (when convenient):   [N] items
+  P3 (backlog or ignore): [N] items
+
+Top 3 P0 items:
+  1. [item] -- /god-hotfix
+  2. [item] -- /god-add-tests
+  3. [item] -- /god-deploy revisit
+
+Suggested next:
+  - Address P0 items first (route via the suggested commands)
+  - /god-update-deps if dependency debt is a P0/P1 driver
+  - /god-upgrade for major-version migrations
+  - Re-run /god-tech-debt quarterly
+```

package/skills/god-test-extension.md

@@ -0,0 +1,87 @@
+---
+name: god-test-extension
+description: |
+  Run contract tests against an extension pack BEFORE publishing.
+  Validates the manifest, checks every declared skill/agent/workflow
+  exists in the pack directory, verifies the engines.godpowers range
+  resolves, and reports findings. Use during pack development.
+
+  Triggers on: "god test extension", "/god-test-extension", "contract
+  test pack", "validate pack"
+---
+
+# /god-test-extension
+
+Run contract tests on a godpowers extension pack source.
+
+## Usage
+
+### `/god-test-extension <source-dir>`
+
+Example:
+- `/god-test-extension ./extensions/security-pack`
+
+## What it checks
+
+| Check | What it asserts |
+|---|---|
+| Manifest exists | `<source-dir>/manifest.yaml` is present |
+| Manifest parses | Valid YAML |
+| apiVersion + kind | `godpowers/v1` + `Extension` |
+| metadata.name | Scoped npm-style: `@org/name` |
+| metadata.version | SemVer `X.Y.Z` |
+| engines.godpowers | Resolves to a non-empty SemVer range |
+| provides | Has at least one of agents/skills/workflows |
+| Provided agents exist | Each `provides.agents[i]` has a file at `<source-dir>/agents/<name>.md` |
+| Provided skills exist | Each `provides.skills[i]` is a slash command with a matching `<source-dir>/skills/<name>.md` |
+| Skill frontmatter | Each declared skill has valid frontmatter (name + description) |
+| Agent frontmatter | Each declared agent has valid frontmatter (name + description + tools) |
+| have-nots prefixes | Each prefix matches `[A-Z][A-Z0-9]*` |
+| Activation | At least one activation rule |
+| No prohibited code | No top-level `child_process` calls in pack scripts |
+
+## Output
+
+```
+EXTENSION CONTRACT TEST: ./extensions/security-pack
+
+Manifest: ./extensions/security-pack/manifest.yaml  [OK]
+apiVersion: godpowers/v1                            [OK]
+metadata.name: @godpowers/security-pack             [OK]
+metadata.version: 1.0.0                             [OK]
+engines.godpowers: >=1.0.0 <2.0.0                   [OK]
+
+Provided surface:
+  agents/god-soc2-auditor.md   [OK]
+  agents/god-hipaa-auditor.md  [OK]
+  agents/god-pci-auditor.md    [OK]
+  skills/god-soc2-audit.md     [OK]
+  skills/god-hipaa-audit.md    [OK]
+  skills/god-pci-audit.md      [OK]
+
+Have-nots prefixes: SOC2 HIPAA PCI                  [OK]
+
+Result: 14 checks passed, 0 failed
+Ready to publish.
+```
+
+## Subcommands
+
+### `/god-test-extension <dir>`
+Full contract check.
+
+### `/god-test-extension <dir> --json`
+Machine-readable findings.
+
+### `/god-test-extension <dir> --strict`
+Treat warnings as errors. Use in CI.
+
+## Implementation
+
+Built-in. Calls `lib/extensions.js` and `lib/agent-validator.js`.
+No agent spawn.
+
+## Related
+
+- `/god-agent-audit` - validate agents in the main repo
+- `/god-extension-add` - install a passing pack