godpowers 1.6.19 → 1.6.21

package/routing/god-story-build.yaml

@@ -10,9 +10,18 @@ prerequisites:
     - .godpowers/stories/STORY-*.md
 
 execution:
-  spawns: [god-planner+god-executor+reviewers]
+  spawns: [god-planner]
   context: fresh
-  writes: []
+  secondary-spawns: [god-executor, god-spec-reviewer, god-quality-reviewer]
+  writes:
+    - .godpowers/stories/STORY-*.md
+    - source code
+
+standards:
+  substitution-test: true
+  three-label-test: true
+  have-nots: [B-01, B-02, B-03, B-04, B-05, B-06, B-07, B-08, B-09, B-10, B-11, B-12]
+  gate-on-failure: pause-for-user
 
 success-path:
   next-recommended: /god-story-verify

package/routing/god-sync.yaml

@@ -30,4 +30,4 @@ failure-path:
 
 endoff:
   state-update: tier statuses updated based on what was synced
-  events: [artifact.updated, have-nots.check, agent.end]
+  events: [agent.start, artifact.updated, have-nots.check, agent.end]

package/routing/recipes/automation-setup.yaml

@@ -0,0 +1,25 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: automation-setup
+  category: maintaining
+  description: "Set up and verify native Godpowers automations"
+
+triggers:
+  intent-keywords:
+    - "create automation"
+    - "set up automation"
+    - "recurring godpowers"
+    - "weekly automation"
+    - "automation status"
+
+sequences:
+  default:
+    description: "Set up and verify native Godpowers automations"
+    steps:
+      - command: "/god-automation-setup"
+        why: "Create approved host-native automation"
+      - command: "/god-automation-status"
+        why: "Confirm configured providers and active templates"
+
+default-sequence: default

package/routing/recipes/context-refresh.yaml

@@ -0,0 +1,26 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: context-refresh
+  category: knowledge
+  description: "Refresh agent context after repo, docs, or workflow changes"
+
+triggers:
+  intent-keywords:
+    - "context refresh"
+    - "update agent context"
+    - "make agents aware"
+    - "new godpowers features"
+
+sequences:
+  default:
+    description: "Refresh agent context after repo, docs, or workflow changes"
+    steps:
+      - command: "/god-context"
+        why: "Refresh portable agent context files"
+      - command: "/god-sync"
+        why: "Apply feature-awareness and Pillars sync checks"
+      - command: "/god-status"
+        why: "Confirm proactive checks are fresh"
+
+default-sequence: default

package/routing/recipes/release-maintenance.yaml

@@ -0,0 +1,27 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: release-maintenance
+  category: maintaining
+  description: "Release closeout, package, docs, and published-surface maintenance"
+
+triggers:
+  intent-keywords:
+    - "create release"
+    - "publish npm"
+    - "update readme badge"
+    - "release notes"
+    - "package release"
+
+sequences:
+  default:
+    description: "Release closeout, package, docs, and published-surface maintenance"
+    steps:
+      - command: "/god-sync"
+        why: "Refresh project artifacts and repo surface checks before release work"
+      - command: "/god-docs"
+        why: "Verify README, release notes, badges, and public docs against code"
+      - command: "/god-version"
+        why: "Confirm installed runtime and package version visibility"
+
+default-sequence: default

package/routing/recipes/story-work.yaml

@@ -0,0 +1,29 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: story-work
+  category: feature-addition
+  description: "Create, build, verify, and close a scoped story"
+
+triggers:
+  intent-keywords:
+    - "create story"
+    - "build story"
+    - "implement story"
+    - "verify story"
+    - "close story"
+
+sequences:
+  default:
+    description: "Create, build, verify, and close a scoped story"
+    steps:
+      - command: "/god-story"
+        why: "Create or select a runtime-testable story"
+      - command: "/god-story-build"
+        why: "Plan and implement the selected story with reviewers"
+      - command: "/god-story-verify"
+        why: "Runtime-test the story acceptance criteria"
+      - command: "/god-story-close"
+        why: "Close the story only after verification passes"
+
+default-sequence: default

package/skills/god-doctor.md

@@ -131,7 +131,8 @@ security prose needs judgment.
 For initialized projects, `/god-doctor` calls `lib/repo-surface-sync.detect`
 as a read-only diagnostic. It reports structural drift across command routing,
 package payload rules, agent spawn targets, workflow metadata, recipe command
-routes, extension packs, and release policy checks.
+routes, extension packs, route quality, recipe coverage, release surfaces, and
+release policy checks.
 
 `/god-doctor --fix` may call
 `lib/repo-surface-sync.run(projectRoot, { fixRouting: true })` to create
@@ -149,6 +150,12 @@ Built-in, no spawned agent. Reads:
 - `lib/repo-doc-sync.detect(projectRoot)` for repo documentation freshness
 - `lib/repo-surface-sync.detect(projectRoot)` for structural repo surface
   freshness
+- `lib/route-quality-sync.detect(projectRoot)` through repo surface sync for
+  atomic spawn and contextual route exit freshness
+- `lib/recipe-coverage-sync.detect(projectRoot)` through repo surface sync for
+  high-frequency intent recipe coverage freshness
+- `lib/release-surface-sync.detect(projectRoot)` through repo surface sync for
+  release-facing surface freshness
 - `bin/install.js` VERSION constant
 
 ## Exit codes

package/skills/god-sync.md

@@ -41,9 +41,10 @@ User runs `/god-sync` after manual changes. Useful for:
    Narrative drift should recommend or spawn `god-docs-writer`.
 5. Call `lib/repo-surface-sync.run(projectRoot)` so command routing, package
    payload, agent handoffs, workflow metadata, recipe routes, extension packs,
-   and release policy are checked before sync closes. Structural drift should
-   recommend scoped agents such as `god-auditor`, `god-roadmap-reconciler`, or
-   `god-coordinator`.
+   route quality, recipe coverage, release surfaces, and release policy are
+   checked before sync closes. Structural drift should recommend scoped agents
+   such as `god-auditor`, `god-roadmap-reconciler`, `god-coordinator`, or
+   `god-docs-writer`.
 6. If repo documentation changed durable project truth, plan or apply Pillars
    updates through `lib/pillars.planArtifactSync` or
    `lib/pillars.applyArtifactSync` under the active Pillars policy.
@@ -63,7 +64,7 @@ Auto-invoked:
   Trigger: <manual /god-sync, recipe closeout, /god-mode final sync, or other source>
   Agent: god-updater
   Local syncs:
-    - pending: feature-awareness, reverse-sync, source-sync, repo-doc-sync, repo-surface-sync, pillars-sync, checkpoint-sync, context-refresh
+    - pending: feature-awareness, reverse-sync, source-sync, repo-doc-sync, repo-surface-sync, route-quality-sync, recipe-coverage-sync, release-surface-sync, pillars-sync, checkpoint-sync, context-refresh
   Artifacts: pending
   Log: .godpowers/SYNC-LOG.md
 ```
@@ -92,6 +93,9 @@ Sync status:
     + source-sync: <written GSD/BMAD/Superpowers companion files, no-op, or skipped>
     + repo-doc-sync: <refreshed README badges/counts, recommended god-docs-writer, or no-op>
     + repo-surface-sync: <checked routes/package/agents/workflows/extensions, recommended scoped agents, or no-op>
+    + route-quality-sync: <checked atomic spawns and contextual exits, no-op, or recommended god-auditor>
+    + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-roadmap-reconciler>
+    + release-surface-sync: <checked badges/changelog/release/package guards, no-op, or recommended god-docs-writer>
     + pillars-sync: <updated N pillar files, no-op, or proposed>
     + checkpoint-sync: <CHECKPOINT.md updated or skipped>
     + context-refresh: <updated AGENTS.md/tool pointers, no-op, or skipped by setting>

package/skills/god-version.md

@@ -16,7 +16,7 @@ Print version and a short capability summary.
 ```
 Godpowers v1.6.19
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 109 skills, 40 agents, 13 workflows, 36 recipes
+Surface: 109 skills, 40 agents, 13 workflows, 40 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync