godpowers 0.15.2 → 0.15.3

package/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to Godpowers will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.15.3] - 2026-05-11
+
+Documentation refresh release. Aligns the public docs, architecture map,
+roadmap, command examples, and extension examples with the shipped v0.15
+surface.
+
+### Changed
+- Updated command and agent counts across README, reference docs, roadmap,
+  architecture docs, and command examples.
+- Documented the installed runtime root path convention for routing, recipes,
+  workflows, and runtime modules.
+- Refreshed extension examples to match first-party pack versions and current
+  Godpowers engine compatibility.
+
 ## [0.15.2] - 2026-05-11
 
 Runtime hardening release. Fixes packaging and workflow edge cases found by

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-0.15.2-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.3-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
 
 **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -223,7 +223,7 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 
 - [Getting Started](docs/getting-started.md)
 - [Concepts](docs/concepts.md)
-- [Command reference (all 82 skills + 38 agents)](docs/reference.md)
+- [Command reference (all 105 skills + 38 agents)](docs/reference.md)
 - [Roadmap](docs/ROADMAP.md)
 - [Changelog](CHANGELOG.md)
 - [Inspiration](INSPIRATION.md)

package/agents/god-orchestrator.md

@@ -28,7 +28,7 @@ You and only you are responsible for:
 1. **Reading the defense** - mode detection (greenfield/brownfield/bluefield/audit)
    and scale detection.
 2. **Calling the play** - selecting the next specialist agent for each tier
-   sub-step from `routing/<command>.yaml`.
+   sub-step from `<runtimeRoot>/routing/<command>.yaml`.
 3. **Owning the playbook** - all writes to `state.json`, `PROGRESS.md`,
    `intent.yaml`, and `events.jsonl` originate from you or agents you spawn.
 4. **Audibles** - handling pause checkpoints, the critical-finding gate, and
@@ -140,9 +140,11 @@ Before each tier, check whether this repo is part of a registered suite:
 
 ## Routing-Driven Decisions
 
-For routing decisions, consult `routing/<command>.yaml` files (installed at
-`<runtime>/godpowers-routing/`). These define prerequisites, success-paths,
-standards checks, and endoff for each command.
+For routing decisions, consult `<runtimeRoot>/routing/<command>.yaml` files.
+When running from a repository checkout, `<runtimeRoot>` is the project root.
+When installed into an AI tool, `<runtimeRoot>` is
+`<tool-config-dir>/godpowers-runtime`. These files define prerequisites,
+success-paths, standards checks, and endoff for each command.
 
 When deciding what to spawn next, query the routing definition:
 - `prerequisites.required` -> what must be done first
@@ -159,11 +161,10 @@ producing agent's own self-check would miss.
 ## Recipe-Driven Decisions (for fuzzy intent)
 
 When the user describes intent in plain English instead of running a specific
-command, consult `routing/recipes/*.yaml` (installed at
-`<runtime>/godpowers-routing/recipes/`). These are scenario-based recipes
-that map fuzzy intent to specific command sequences.
+command, consult `<runtimeRoot>/routing/recipes/*.yaml`. These are
+scenario-based recipes that map fuzzy intent to specific command sequences.
 
-Programmatic access via `lib/recipes.js`:
+Programmatic access via `<runtimeRoot>/lib/recipes.js`:
 - `matchIntent(text, projectRoot)` -> ranked recipe matches by keyword
 - `suggestForState(projectRoot)` -> recipes matching current lifecycle phase
 - `getRecipe(name)` -> lookup specific recipe
@@ -175,8 +176,8 @@ function returns the `add-feature-mid-arc-pause` recipe with sequence
 with the "why" annotations for each step.
 
 This is the third layer of decision support:
-1. **Routing** (routing/<command>.yaml): structural prerequisites and gates
-2. **Recipes** (routing/recipes/<recipe>.yaml): scenario-based sequences
+1. **Routing** (`<runtimeRoot>/routing/<command>.yaml`): structural prerequisites and gates
+2. **Recipes** (`<runtimeRoot>/routing/recipes/<recipe>.yaml`): scenario-based sequences
 3. **Standards** (god-standards-check): quality gates between stages
 
 ## Detection-Driven Tier 1 Routing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.2",
+  "version": "0.15.3",
   "description": "AI-powered development system: 104 slash commands and 38 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/skills/god-doctor.md

@@ -46,9 +46,9 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 82 skills installed
+  [OK] 105 skills installed
   [OK] 38 agents installed
-  [OK] VERSION matches (0.12.0)
+  [OK] VERSION matches (0.15.3)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/

package/skills/god-extension-add.md

@@ -22,8 +22,8 @@ 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.
+  First-party packs are publish-ready npm packages; local directories
+  remain supported for development and private packs.
 
 ## Process
 

package/skills/god-extension-info.md

@@ -23,7 +23,7 @@ Example:
 ## Output
 
 ```
-EXTENSION: @godpowers/security-pack v1.0.0
+EXTENSION: @godpowers/security-pack v0.1.0
 Path: ~/.claude/godpowers-extensions/@godpowers/security-pack
 Description:
   Compliance-aware security agents for SOC 2, HIPAA, and PCI-DSS
@@ -31,7 +31,7 @@ Description:
   specific checks.
 
 Engines:
-  godpowers: >=1.0.0 <2.0.0   (compatible with running v0.13.0? YES)
+  godpowers: >=0.14.0 <2.0.0  (compatible with running v0.15.3? YES)
 
 Provides:
   Agents (3):

package/skills/god-extension-list.md

@@ -18,17 +18,17 @@ List installed godpowers extensions.
 ```
 INSTALLED EXTENSIONS (3)
 
-@godpowers/security-pack  v1.0.0
+@godpowers/security-pack  v0.1.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
+@godpowers/launch-pack    v0.1.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
+@godpowers/data-pack      v0.1.0
   Path: ~/.claude/godpowers-extensions/@godpowers/data-pack
   Skills: /god-etl, /god-ml-feature, /god-dashboard
 ```

package/skills/god-test-extension.md

@@ -49,7 +49,7 @@ 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]
+engines.godpowers: >=0.14.0 <2.0.0                  [OK]
 
 Provided surface:
   agents/god-soc2-auditor.md   [OK]

package/skills/god-version.md

@@ -14,9 +14,9 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v0.12.0
+Godpowers v0.15.3
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 82 skills, 38 agents, 13 workflows, 36 recipes
+Surface: 105 skills, 38 agents, 13 workflows, 36 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 ```