godpowers 0.15.0

package/skills/god-extension-add.md

@@ -0,0 +1,79 @@
+---
+name: god-extension-add
+description: |
+  Install a godpowers extension pack from a local directory or
+  scaffolded extensions/. Validates the manifest, checks the engines
+  compatibility range against the running godpowers version, then
+  copies the pack into <runtime>/godpowers-extensions/.
+
+  Triggers on: "god extension add", "/god-extension-add", "install
+  pack", "install extension"
+---
+
+# /god-extension-add
+
+Install a godpowers extension pack.
+
+## Usage
+
+### `/god-extension-add <source>`
+
+Where `<source>` is either:
+- An absolute or relative path to a directory containing `manifest.yaml`
+  (e.g. `./extensions/security-pack`)
+- A scoped npm package name (e.g. `@godpowers/security-pack`).
+  In v0.13.0 only local directories are supported; npm install is on
+  the v0.14 ramp.
+
+## Process
+
+1. Resolve `<source>` to a directory with `manifest.yaml`.
+2. Parse the manifest. Reject on parse errors.
+3. Validate against `schema/extension-manifest.v1.json`:
+   - apiVersion, kind, metadata.name (scoped), metadata.version (semver)
+   - engines.godpowers range
+   - provides block
+4. **Capability handshake**: verify the manifest's
+   `engines.godpowers` range includes the running godpowers version
+   (read from `<runtime>/GODPOWERS_VERSION` or `package.json`).
+   Reject on mismatch with a clear message.
+5. Copy the pack contents to
+   `<runtime>/godpowers-extensions/<pack-name>/`:
+   - manifest.yaml
+   - agents/, skills/, workflows/, references/ (if present)
+6. Append `op:extension.install` to reflog + emit
+   `extension.install` event.
+7. **Lazy activation**: do NOT load the pack's agents/skills now.
+   They're loaded on first invocation of one of their slash commands.
+8. Report: pack installed, list provided agents/skills/workflows.
+
+## Subcommands
+
+### `/god-extension-add <source>`
+Install with capability check.
+
+### `/god-extension-add <source> --force`
+Skip the capability handshake. Use only when you know what you're doing
+and accept that the pack may misbehave on a mismatched godpowers.
+
+### `/god-extension-add <source> --dry-run`
+Validate the manifest; do not copy.
+
+## Safety
+
+- Never installs a pack that fails the capability handshake without
+  `--force`.
+- Never executes scripts from the pack at install time. Pack code only
+  runs when one of its slash commands is invoked.
+
+## Implementation
+
+Built-in. Calls `lib/extensions.js install(...)`.
+
+## Related
+
+- `/god-extension-list` - show installed extensions
+- `/god-extension-info @x/y` - details of one extension
+- `/god-extension-remove @x/y` - uninstall
+- `/god-test-extension <path>` - run contract tests on a pack before
+  publishing

package/skills/god-extension-info.md

@@ -0,0 +1,75 @@
+---
+name: god-extension-info
+description: |
+  Show details of one installed godpowers extension pack: manifest,
+  provided surface, activation rules, install path, version
+  compatibility.
+
+  Triggers on: "god extension info", "/god-extension-info", "show
+  pack details", "what does X pack do"
+---
+
+# /god-extension-info
+
+Show details for one installed extension.
+
+## Usage
+
+### `/god-extension-info <pack-name>`
+
+Example:
+- `/god-extension-info @godpowers/security-pack`
+
+## Output
+
+```
+EXTENSION: @godpowers/security-pack v1.0.0
+Path: ~/.claude/godpowers-extensions/@godpowers/security-pack
+Description:
+  Compliance-aware security agents for SOC 2, HIPAA, and PCI-DSS
+  audits. Layers on top of god-harden-auditor with regulation-
+  specific checks.
+
+Engines:
+  godpowers: >=1.0.0 <2.0.0   (compatible with running v0.13.0? YES)
+
+Provides:
+  Agents (3):
+    - god-soc2-auditor
+    - god-hipaa-auditor
+    - god-pci-auditor
+  Skills (3):
+    - /god-soc2-audit
+    - /god-hipaa-audit
+    - /god-pci-audit
+  Workflows (3):
+    - soc2-arc, hipaa-arc, pci-arc
+  Have-nots prefixes:
+    - SOC2  (SOC 2 Common Criteria)
+    - HIPAA (Security Rule 164.308/310/312)
+    - PCI   (PCI-DSS 4.0)
+
+Activation (lazy; loads on first call):
+  - /god-soc2-audit
+  - /god-hipaa-audit
+  - /god-pci-audit
+  - /god-extension-list
+```
+
+## Subcommands
+
+### `/god-extension-info <name>`
+Single pack details.
+
+### `/god-extension-info <name> --json`
+Machine-readable.
+
+## Implementation
+
+Built-in. Calls `lib/extensions.js info(runtimeConfigDir, packName)`.
+
+## Related
+
+- `/god-extension-list` - all installed packs
+- `/god-extension-add` - install
+- `/god-extension-remove` - uninstall

package/skills/god-extension-list.md

@@ -0,0 +1,55 @@
+---
+name: god-extension-list
+description: |
+  Show all godpowers extension packs currently installed in the
+  active runtime. Each entry: name, version, install path, summary
+  of what it provides.
+
+  Triggers on: "god extension list", "/god-extension-list", "what
+  extensions are installed", "show packs"
+---
+
+# /god-extension-list
+
+List installed godpowers extensions.
+
+## Output
+
+```
+INSTALLED EXTENSIONS (3)
+
+@godpowers/security-pack  v1.0.0
+  Path: ~/.claude/godpowers-extensions/@godpowers/security-pack
+  Skills: /god-soc2-audit, /god-hipaa-audit, /god-pci-audit
+  Agents: god-soc2-auditor, god-hipaa-auditor, god-pci-auditor
+  Workflows: soc2-arc, hipaa-arc, pci-arc
+
+@godpowers/launch-pack    v1.0.0
+  Path: ~/.claude/godpowers-extensions/@godpowers/launch-pack
+  Skills: /god-show-hn, /god-product-hunt, /god-indie-hackers, /god-oss-release
+
+@godpowers/data-pack      v0.9.0
+  Path: ~/.claude/godpowers-extensions/@godpowers/data-pack
+  Skills: /god-etl, /god-ml-feature, /god-dashboard
+```
+
+## Subcommands
+
+### `/god-extension-list`
+List all installed packs (summary view).
+
+### `/god-extension-list --json`
+Machine-readable output.
+
+### `/god-extension-list --verbose`
+Include manifest activation rules + have-nots prefixes for each pack.
+
+## Implementation
+
+Built-in. Calls `lib/extensions.js list(runtimeConfigDir)`.
+
+## Related
+
+- `/god-extension-add` - install a pack
+- `/god-extension-info @x/y` - one pack in detail
+- `/god-extension-remove` - uninstall

package/skills/god-extension-remove.md

@@ -0,0 +1,66 @@
+---
+name: god-extension-remove
+description: |
+  Uninstall a godpowers extension pack. Removes the pack's directory
+  under <runtime>/godpowers-extensions/. Does NOT delete project-level
+  data the pack may have written (e.g. SOC2 audit findings). Reversible
+  by re-installing.
+
+  Triggers on: "god extension remove", "/god-extension-remove",
+  "uninstall pack", "remove extension"
+---
+
+# /god-extension-remove
+
+Uninstall a godpowers extension pack.
+
+## Usage
+
+### `/god-extension-remove <pack-name>`
+
+Example:
+- `/god-extension-remove @godpowers/launch-pack`
+
+## Process
+
+1. Resolve `<pack-name>` to its installed path via
+   `lib/extensions.info(runtimeConfigDir, packName)`.
+2. If not found: report `not-installed` and exit.
+3. Confirm with user: pack name, version, install path, what will be removed.
+4. On confirmation: `fs.rmSync(packPath, { recursive: true, force: true })`.
+5. Append `op:extension.remove` to reflog + emit `extension.remove` event.
+6. Report: pack removed, list invalidated commands.
+
+## What this does NOT remove
+
+- Project-level artifacts the pack produced (e.g.
+  `.godpowers/audits/soc2-2026-01.md`). These stay; re-install the
+  pack to read them again.
+- Have-nots IDs already recorded in linkage. Those references become
+  dead until the pack is re-installed.
+
+## Subcommands
+
+### `/god-extension-remove <name>`
+Interactive uninstall (asks for confirmation).
+
+### `/god-extension-remove <name> --yes`
+Skip confirmation.
+
+### `/god-extension-remove <name> --dry-run`
+Show what would be removed.
+
+## Recovery
+
+Re-install with `/god-extension-add` (no state is lost on the
+project side).
+
+## Implementation
+
+Built-in. Calls `lib/extensions.js remove(runtimeConfigDir, packName)`.
+
+## Related
+
+- `/god-extension-add` - install
+- `/god-extension-list` - what's installed
+- `/god-extension-info` - one pack in detail

package/skills/god-extract-learnings.md

@@ -0,0 +1,60 @@
+---
+name: god-extract-learnings
+description: |
+  Extract decisions, lessons, patterns, and surprises from completed phase
+  artifacts. Captures institutional knowledge for future projects.
+
+  Triggers on: "god extract learnings", "/god-extract-learnings", "lessons learned",
+  "what did we learn"
+---
+
+# /god-extract-learnings
+
+Capture institutional knowledge from a completed phase or milestone.
+
+## When to use
+
+- After completing a milestone (Now -> Done)
+- After a successful /god-mode arc
+- Before a /god-postmortem (different focus: that's for incidents)
+
+## Process
+
+1. Read all artifacts from the completed phase:
+   - PRD, ARCH, ROADMAP, STACK, build PLAN, deploy STATE, etc.
+2. Extract:
+   - **Decisions made**: with their flip points
+   - **Lessons learned**: what would you do differently next time
+   - **Patterns established**: techniques that worked, worth reusing
+   - **Surprises**: things you didn't expect (good or bad)
+3. Write to `.godpowers/learnings/<milestone>/LEARNINGS.md`
+4. Optionally append summary to a global `~/.godpowers-knowledge.md` for
+   cross-project learning (opt-in)
+
+## Output
+
+```markdown
+# Learnings: [milestone]
+
+## Decisions
+- [DECISION] Used Postgres over MongoDB. Flip point: document data.
+  Outcome: held up; no flip needed.
+
+## Lessons Learned
+- The Stripe webhook signature verification took 2 days longer than estimated;
+  budget more for crypto-related work.
+
+## Patterns Worth Reusing
+- The "1 user_id, multiple stripe_account_id" data model. Reusable for any
+  multi-account integration.
+
+## Surprises
+- Users wanted CSV export much earlier than we expected. Bumped from COULD
+  to MUST in V1.1.
+```
+
+## Have-Nots
+
+- Generic lessons ("communicate better")
+- No flip-point references (decisions without context)
+- Missing surprises (everything went perfectly: implausible)

package/skills/god-fast.md

@@ -0,0 +1,47 @@
+---
+name: god-fast
+description: |
+  Make a quick inline edit without full Godpowers planning overhead. For trivial
+  changes: typo fixes, config tweaks, single-line updates. No agents, no plans,
+  no PROGRESS.md updates.
+
+  Triggers on: "god fast", "/god-fast", "quick fix", "trivial change", "tiny tweak"
+---
+
+# /god-fast
+
+Skip the full pipeline. Make a small edit inline.
+
+## When to use
+
+- Single-line bug fix
+- Config tweak (port number, env var name)
+- Typo correction
+- Documentation typo
+- One-character syntax fix
+
+## When NOT to use
+
+- Anything that affects user-visible behavior -> use /god-build
+- Anything without an existing test -> use /god-build (TDD)
+- Anything you can't describe in one sentence
+
+## Process
+
+1. Make the edit directly. No planner, no executor, no reviewer.
+2. Run the existing test suite to verify nothing broke.
+3. Commit with a one-line message.
+
+## Guardrails
+
+- If running tests reveals regressions: STOP. Switch to /god-build or /god-debug.
+- If the change touches more than 3 lines: STOP. Switch to /god-build.
+- Skip PROGRESS.md updates (this is below the planning threshold).
+
+## On Completion
+
+```
+Quick fix applied: [one-line description]
+Tests: [N] passed
+Commit: [SHA]
+```

package/skills/god-feature.md

@@ -0,0 +1,114 @@
+---
+name: god-feature
+description: |
+  Add a feature to an existing project. Skips the full-arc 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.
+
+  Triggers on: "god feature", "/god-feature", "add a feature", "new feature",
+  "build feature"
+---
+
+# /god-feature
+
+Add a feature to an already-existing project.
+
+## When to use
+
+- You have a working app with deployed code
+- You want to add a discrete feature
+- Full /god-mode would be overkill (it'd re-run PRD/ARCH/STACK for the whole product)
+
+## When NOT to use
+
+- New project: use /god-mode
+- Trivial change: use /god-fast or /god-quick
+- Refactor: use /god-refactor
+- Bug fix: use /god-debug or /god-hotfix
+
+## Setup
+
+1. Verify `.godpowers/` exists. If not, fall back to /god-init first.
+2. Read existing PRD, ARCH, ROADMAP for context
+
+## Orchestration
+
+### Phase 1: Mini-PRD
+Spawn **god-pm** in fresh context with instructions:
+"This is a feature addition to an existing product. Write a feature-scoped
+PRD section. The product PRD already exists at .godpowers/prd/PRD.md; do NOT
+rewrite it. Append the feature spec to .godpowers/features/<feature-slug>/PRD.md."
+
+### Phase 2: Micro-architecture (conditional)
+If the feature touches new architectural ground:
+Spawn **god-architect** with instructions:
+"Existing ARCH.md describes the system. This feature extends it. Write only
+the architectural deltas to .godpowers/features/<feature-slug>/ARCH-DELTA.md
+and update relevant ADRs."
+
+If the feature fits within existing architecture: skip this phase.
+
+### Phase 3: Plan and Build
+Spawn **god-planner** scoped to the feature only.
+Then run god-executor + god-spec-reviewer + god-quality-reviewer per slice.
+
+### Phase 4: Deploy
+Use existing deploy pipeline (.godpowers/deploy/STATE.md). No new pipeline.
+Feature flag the rollout if the feature is high-risk.
+
+### Phase 5: Harden (just the new code)
+Spawn **god-harden-auditor** with instructions:
+"Review only the new code added for this feature. Existing code already
+audited at .godpowers/harden/FINDINGS.md."
+
+### Phase 6: Soft launch
+No landing page. No marketing. The feature ships behind a flag, gradually
+enabled. Update CHANGELOG.
+
+## On Completion
+
+```
+Feature complete: .godpowers/features/<feature-slug>/
+
+Suggested next: /god-status (see overall project state)
+Or: /god-feature for the next feature
+```
+
+## Linkage and reverse-sync
+
+Per Phase 13 of the production-ready plan, this workflow participates
+in the linkage system:
+
+- On completion of any code change, `lib/reverse-sync.run(projectRoot)`
+  is called via god-updater. This:
+  - Scans new/modified code for linkage annotations (// Implements: P-MUST-NN, etc.)
+  - Updates `.godpowers/links/{artifact-to-code,code-to-artifact}.json`
+  - Detects drift via `lib/drift-detector`
+  - Appends fenced footers to PRD/ARCH/ROADMAP/STACK/DESIGN
+  - Surfaces drift findings to REVIEW-REQUIRED.md
+
+- Stable IDs MUST be used in artifact deltas (P-MUST-NN, ADR-NNN,
+  C-{slug}, M-{slug}, S-{slug}, D-{slug}, token paths). The scanner
+  picks them up automatically via comment annotations.
+
+- For UI work: agent-browser audit may run as part of /god-build
+  post-wave or /god-launch gate (see `/god-test-runtime`).
+
+- Findings flow into the standard REVIEW-REQUIRED.md walkthrough
+  via `/god-review-changes`.
+
+
+## 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-graph.md

@@ -0,0 +1,56 @@
+---
+name: god-graph
+description: |
+  Build, query, and inspect the project knowledge graph. Connects PRD
+  requirements to architecture decisions to roadmap milestones to build
+  slices to deploy artifacts.
+
+  Triggers on: "god graph", "/god-graph", "knowledge graph", "trace requirement"
+---
+
+# /god-graph
+
+Connect-the-dots across all artifacts.
+
+## What the graph encodes
+
+Nodes:
+- Requirements (from PRD)
+- ADRs (from ARCH)
+- Milestones (from ROADMAP)
+- Slices (from BUILD/PLAN)
+- Commits
+- Have-nots
+- Open questions
+
+Edges:
+- Requirement -> ADR (NFR -> architectural choice)
+- ADR -> Slice (decision -> implementation)
+- Slice -> Commit (plan -> code)
+- Have-not -> Artifact (failure mode -> what it applies to)
+- Open question -> Phase (when due)
+
+## Subcommands
+
+### `/god-graph build`
+Walk all artifacts in `.godpowers/`, build the graph, write to
+`.godpowers/graph/GRAPH.json`.
+
+### `/god-graph trace <node>`
+Show all edges from a specific node. Example:
+`/god-graph trace requirement:user-can-export-csv`
+Shows which ADR addresses it, which milestone delivers it, which slices
+implement it, which commits it landed in.
+
+### `/god-graph orphans`
+Show nodes with no edges. Likely: requirements never delivered, ADRs
+never referenced, slices never reviewed.
+
+### `/god-graph render`
+Render an ASCII or Mermaid visualization to `.godpowers/graph/GRAPH.md`.
+
+## Why this matters
+
+- "Did we build everything in the PRD?" -> orphan check on requirements
+- "Why did we make this choice?" -> trace from code back to ADR
+- "What's the impact of changing X?" -> trace edges from X

package/skills/god-harden.md

@@ -0,0 +1,106 @@
+---
+name: god-harden
+description: |
+  Adversarial security review. Spawns the god-harden-auditor agent in a fresh
+  context. Critical findings BLOCK launch.
+
+  Triggers on: "god harden", "/god-harden", "security review", "OWASP", "pen test"
+---
+
+# /god-harden
+
+Spawn the **god-harden-auditor** agent in a fresh context via Task tool.
+
+## Setup
+
+1. Verify build is complete (`.godpowers/build/STATE.md` exists).
+2. Spawn god-harden-auditor with full code access.
+3. The agent writes `.godpowers/harden/FINDINGS.md`.
+
+## Verification
+
+After god-harden-auditor returns:
+1. Verify FINDINGS.md exists on disk
+2. Read findings classification:
+   - If any Critical: PROGRESS.md status = failed, launch is BLOCKED
+   - If only High/Medium/Low: PROGRESS.md status = done
+
+## Have-Nots
+
+Hardening FAILS if:
+- Only automated scanner output, no manual review
+- Auth boundaries not tested (just code-read)
+- No input validation audit
+- Rate limiting not verified
+- OWASP categories skipped without justification
+- Findings have no severity classification
+
+## Critical-Finding Gate
+
+If ANY finding is Critical:
+1. Pause god-mode immediately
+2. Present finding to user using pause format
+3. Launch remains BLOCKED until:
+   - Critical finding is fixed and re-verified, OR
+   - User explicitly accepts the risk in writing
+
+## On Completion
+
+If FINDINGS.md has 0 Critical findings:
+```
+Harden complete: .godpowers/harden/FINDINGS.md
+[N] High, [N] Medium, [N] Low. 0 Critical. Launch gate: PASSED.
+
+Suggested next: /god-launch (put it in front of users)
+```
+
+If FINDINGS.md has Critical findings:
+```
+Harden complete: .godpowers/harden/FINDINGS.md
+[N] CRITICAL findings. Launch gate: BLOCKED.
+
+Suggested next: Resolve Critical findings, then re-run /god-harden.
+Use /god-debug if you need help with the fix.
+```
+
+
+## Re-invocation contract
+
+What happens if `/god-harden` is run when `.godpowers/harden/FINDINGS.md` already exists:
+
+| Existing state | Behavior |
+|---|---|
+| File does not exist | Spawn god-harden-auditor; produce file; mark sub-step done |
+| File exists, passes lint, state.json says `done` | Pause: ask user (A) re-run anyway with diff preview, (B) treat as imported (no-op), (C) cancel |
+| File exists, fails lint or have-nots | Spawn god-harden-auditor in update mode with current file + findings as input. Diff preview before overwrite. |
+| File exists, state.json says `pending` | Treat as imported: hash + register, no agent spawn. User can `/god-harden --force` to re-run. |
+| `--force` flag passed | Snapshot existing file to `.godpowers/.trash/god-harden-<ts>/`. Spawn agent fresh. |
+| `--dry-run` flag passed | Show what would happen; touch nothing |
+
+Snapshots in `.trash/` are recoverable via `/god-restore` for 30 days.
+The reflog records every god-harden invocation as `op:god-harden` for `/god-undo`.
+
+### Idempotency guarantees
+
+- Running `/god-harden` twice with no user input between them is a no-op
+  (second call detects the artifact and pauses).
+- Running `/god-harden --dry-run` is always read-only.
+- An interrupted `/god-harden` (agent crashes mid-run) leaves state.json
+  with `status: failed` and the artifact path either missing or marked
+  for `/god-repair` review. Re-running picks up cleanly.
+
+
+## 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.