godpowers 1.6.0 → 1.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (10) hide show
  1. package/CHANGELOG.md +36 -0
  2. package/README.md +4 -4
  3. package/RELEASE.md +34 -31
  4. package/lib/README.md +73 -21
  5. package/package.json +7 -3
  6. package/references/building/README.md +7 -9
  7. package/references/planning/README.md +11 -8
  8. package/references/shipping/README.md +11 -10
  9. package/skills/god-doctor.md +1 -1
  10. package/skills/god-version.md +1 -1
package/CHANGELOG.md CHANGED
@@ -5,6 +5,40 @@ All notable changes to Godpowers will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.6.1] - 2026-05-15
9
+
10
+ Release hardening patch. Keeps the 1.6 domain precision surface stable while
11
+ making package publication, release checks, and CI verification harder to drift.
12
+
13
+ ### Added
14
+ - Added `npm run release:check`, which runs the full test suite, audit checks,
15
+ and package contents verification.
16
+ - Added `scripts/check-package-contents.js` to assert that the npm payload
17
+ includes load-bearing runtime files and excludes local-only development files.
18
+ - Added `docs/RELEASE-CHECKLIST.md` for versioning, verification, package
19
+ surface, tag, npm provenance, and post-release cleanup.
20
+ - Added an explicit plan-mode E2E smoke test for the `/god-mode` full-arc
21
+ workflow against the `todo-app` fixture.
22
+
23
+ ### Changed
24
+ - CI now uses `npm ci`, runs audit checks, runs the E2E smoke path explicitly,
25
+ and keeps package checks aligned with local npm scripts.
26
+ - Test documentation now describes the current runtime and E2E smoke coverage
27
+ instead of stale scaffold-only plans.
28
+ - Runtime and reference README files now describe the implemented modules and
29
+ reference files instead of placeholder future work.
30
+ - Package tarballs are ignored by git, and package contents checks reject
31
+ generated tarballs.
32
+ - The release script now pushes the git tag and relies on the tag-triggered
33
+ GitHub Actions npm publish workflow for provenance.
34
+
35
+ ### Guardrails
36
+ - This patch does not add new slash commands, agents, workflows, recipes, or
37
+ schemas.
38
+ - The 1.6 domain glossary behavior remains unchanged.
39
+ - Future npm publishes should use the tag-triggered GitHub workflow unless a
40
+ documented emergency requires a manual fallback.
41
+
8
42
  ## [1.6.0] - 2026-05-15
9
43
 
10
44
  Domain precision release. Adds a Godpowers-native vocabulary layer so fuzzy or
@@ -32,6 +66,8 @@ roadmap, stack, docs, or lint artifacts.
32
66
  reverse, surprising without context, and based on a real tradeoff.
33
67
  - Public release metadata, package version, and README badge now point to
34
68
  1.6.0.
69
+ - Release history now has a `v1.6.0` git tag matching the published npm
70
+ package.
35
71
 
36
72
  ### Guardrails
37
73
  - The domain glossary is preparation context only. It does not replace PRD,
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
4
4
  [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
5
- [![Version](https://img.shields.io/badge/version-1.6.0-blue)](CHANGELOG.md)
5
+ [![Version](https://img.shields.io/badge/version-1.6.1-blue)](CHANGELOG.md)
6
6
  [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
7
7
 
8
8
  **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -12,9 +12,9 @@ idea to hardened production. It runs as **slash commands inside your AI coding
12
12
  tool** (Claude Code, Codex, Cursor, etc.) that orchestrate **specialist agents**
13
13
  in fresh contexts to do the work.
14
14
 
15
- Version 1.6.0 adds domain precision: `/god-discuss` can resolve overloaded
16
- project language into `.godpowers/domain/GLOSSARY.md`, and downstream planning,
17
- architecture, stack, roadmap, docs, and lint flows use that vocabulary.
15
+ Version 1.6.1 hardens the release path around the 1.6 domain precision layer:
16
+ release checks now cover tests, audit, package contents, E2E smoke, and npm
17
+ payload verification before publishing.
18
18
 
19
19
  It fuses four disciplines into one unified workflow:
20
20
 
package/RELEASE.md CHANGED
@@ -1,10 +1,11 @@
1
- # Godpowers 1.6.0 Release
1
+ # Godpowers 1.6.1 Release
2
2
 
3
3
  Date: 2026-05-15
4
4
 
5
- Godpowers 1.6.0 adds domain precision. The goal of this release is to keep
6
- project language sharp before it becomes product scope, system shape, delivery
7
- sequence, stack rationale, documentation, or linted artifact text.
5
+ Godpowers 1.6.1 hardens the release and package path around the 1.6 domain
6
+ precision release. The goal of this patch is to make tests, audit checks,
7
+ package contents, E2E smoke coverage, npm publishing, and GitHub release
8
+ metadata easier to verify before anything reaches users.
8
9
 
9
10
  ## What is stable
10
11
 
@@ -18,39 +19,42 @@ sequence, stack rationale, documentation, or linted artifact text.
18
19
  - Core schemas: intent, state, events, workflow, routing, recipes, extension
19
20
  manifests
20
21
  - Extension pack compatibility range for the 1.x line
22
+ - Domain precision through `.godpowers/domain/GLOSSARY.md` and DG-01 through
23
+ DG-05 checks
21
24
 
22
25
  ## What is new
23
26
 
24
- - `/god-discuss` now performs domain grilling during next-phase scoping.
25
- - `.godpowers/domain/GLOSSARY.md` records canonical terms, avoided aliases,
26
- relationships, example dialogue, source notes, and flagged ambiguities.
27
- - `templates/DOMAIN-GLOSSARY.md` provides the native glossary shape.
28
- - `god-explorer` inspects code or docs before asking the user when repo
29
- evidence can answer a domain question.
30
- - PM, architect, roadmapper, stack selector, and docs writer agents now read
31
- `.godpowers/domain/GLOSSARY.md` when present.
32
- - `/god-lint` now recognizes domain glossary artifacts and reports DG-01
33
- through DG-05 findings.
34
- - Architecture guidance now creates ADRs only when a decision is hard to
35
- reverse, surprising without context, and based on a real tradeoff.
36
-
37
- ## What 1.6 means
38
-
39
- Godpowers now has a native vocabulary layer that supports planning without
40
- creating a competing source of truth. The domain glossary is preparation
41
- context. PRD, ARCH, ROADMAP, STACK, docs, and Pillars files still carry the
42
- durable decisions for their own domains.
43
-
44
- The glossary helps agents converge on exact project language before they write
45
- load-bearing artifacts. It is especially useful for brownfield and bluefield
46
- projects where existing docs, code names, org vocabulary, and user intent can
47
- use the same word for different things.
27
+ - `npm run release:check` now runs tests, audit checks, and package contents
28
+ verification as a single pre-release gate.
29
+ - `npm run pack:check` now asserts required npm payload files and rejects
30
+ local-only files instead of relying on visual dry-run output.
31
+ - CI now installs with `npm ci`, runs audit checks, runs E2E smoke explicitly,
32
+ and keeps package validation tied to local scripts.
33
+ - `docs/RELEASE-CHECKLIST.md` documents the expected release flow, tag flow,
34
+ npm provenance path, and post-release verification.
35
+ - `/god-mode` full-arc has a plan-mode E2E smoke test that verifies 10 jobs,
36
+ 7 waves, and a generated `.godpowers/runs/.../plan.yaml` artifact.
37
+ - Stale placeholder docs for runtime libraries, references, and test strategy
38
+ now describe the implemented system.
39
+
40
+ ## What 1.6.1 means
41
+
42
+ Godpowers 1.6.1 does not expand the public command surface. It tightens the
43
+ release discipline around the existing surface so local checks, CI checks, npm
44
+ payload contents, git tags, and GitHub release metadata agree.
45
+
46
+ The domain glossary remains preparation context. PRD, ARCH, ROADMAP, STACK,
47
+ docs, and Pillars files still carry durable decisions for their own domains.
48
48
 
49
49
  ## Stability policy
50
50
 
51
51
  During the 1.x stability window, do not add broad new command families, change
52
52
  schema formats, or rename public artifacts without evidence from real use.
53
53
 
54
+ The `v1.6.1` git tag points to the release commit that matches the npm
55
+ `godpowers@1.6.1` package. Public publishes should prefer the tag-triggered
56
+ GitHub workflow so npm provenance, git history, and release notes stay aligned.
57
+
54
58
  Allowed changes:
55
59
 
56
60
  - Critical bug fixes
@@ -69,6 +73,5 @@ Deferred changes:
69
73
 
70
74
  ## Adoption ask
71
75
 
72
- Use `/god-discuss` before a PRD, feature, refactor, or migration where terms
73
- feel fuzzy. Report where the glossary catches ambiguity early, where it adds
74
- noise, and which domain checks should become stricter.
76
+ Run `npm run release:check` before publishing changes. Report any release path
77
+ step that still depends on memory, manual inspection, or local machine state.
package/lib/README.md CHANGED
@@ -1,28 +1,80 @@
1
- # lib/ - Runtime Library (placeholder)
1
+ # lib/ - Runtime Library
2
2
 
3
- This directory is reserved for v0.5+ runtime modules. v0.4 has the schemas
4
- defined; v0.5 implements them.
3
+ This directory contains the JavaScript runtime modules that support Godpowers
4
+ validation, routing, workflow execution, state management, observability, and
5
+ package-level integrations.
5
6
 
6
- ## Planned modules
7
+ ## Core state and intent
7
8
 
8
- | Module | Purpose | Target version |
9
- |--------|---------|----------------|
10
- | `state.js` | Read/write `.godpowers/state.json` with schema validation | v0.5 |
11
- | `events.js` | Append OpenTelemetry-shape events to events.jsonl | v0.5 |
12
- | `intent.js` | Read/validate `intent.yaml` (or `.godpowers/intent.yaml`) | v0.5 |
13
- | `workflow-runtime.js` | Parse and execute workflow YAML | v0.5 |
14
- | `reflog.js` | Append to `.godpowers/log` and rewind state | v0.6 |
15
- | `trash.js` | Recoverable deletion to `.godpowers/.trash/` | v0.6 |
16
- | `metrics.js` | Compute per-tier stats from events.jsonl | v0.7 |
17
- | `extension-loader.js` | Lazy-activate skill packs | v0.8 |
9
+ | Module | Purpose |
10
+ |--------|---------|
11
+ | `state.js` | Read, initialize, validate, and write `.godpowers/state.json`. |
12
+ | `state-lock.js` | Coordinate state writes with a lock file. |
13
+ | `intent.js` | Read and validate `intent.yaml` from project roots or `.godpowers/`. |
14
+ | `checkpoint.js` | Create and inspect resumable checkpoint artifacts. |
15
+ | `budget.js` | Read and enforce configured budget controls. |
16
+ | `cost-tracker.js` | Track token and cost estimates from event streams. |
18
17
 
19
- ## Why placeholder
18
+ ## Events and observability
20
19
 
21
- In v0.4 (current), Godpowers is markdown skills + agent prose. There's no
22
- runtime that needs these modules; agents read/write artifacts directly.
20
+ | Module | Purpose |
21
+ |--------|---------|
22
+ | `events.js` | Append structured runtime events. |
23
+ | `event-reader.js` | Read and aggregate event streams. |
24
+ | `otel-exporter.js` | Export Godpowers events in an OpenTelemetry-shaped format. |
25
+ | `runtime-audit.js` | Audit runtime health and expected project state. |
26
+ | `runtime-test.js` | Provide runtime checks used by package tests. |
23
27
 
24
- In v0.5+, the workflow runtime needs structured access to state. That's when
25
- these modules ship.
28
+ ## Routing and execution
26
29
 
27
- See `../ARCHITECTURE.md` for the design and `../docs/ROADMAP.md` for the
28
- sequencing.
30
+ | Module | Purpose |
31
+ |--------|---------|
32
+ | `router.js` | Resolve user intent to skills, agents, recipes, and workflows. |
33
+ | `recipes.js` | Load and validate routing recipes. |
34
+ | `workflow-parser.js` | Parse workflow YAML into executable steps. |
35
+ | `workflow-runner.js` | Execute workflow steps with validation hooks. |
36
+ | `agent-cache.js` | Cache agent metadata for faster routing. |
37
+ | `agent-validator.js` | Validate agent frontmatter and contracts. |
38
+
39
+ ## Artifact quality
40
+
41
+ | Module | Purpose |
42
+ |--------|---------|
43
+ | `artifact-linter.js` | Check artifacts for required labels, evidence, and domain precision. |
44
+ | `artifact-diff.js` | Compare artifact changes for review and release workflows. |
45
+ | `have-nots-validator.js` | Check artifacts against known failure modes. |
46
+ | `meta-linter.js` | Validate Godpowers documentation and skill metadata. |
47
+ | `story-validator.js` | Validate story artifacts and story lifecycle state. |
48
+
49
+ ## Design, context, and integrations
50
+
51
+ | Module | Purpose |
52
+ |--------|---------|
53
+ | `context-writer.js` | Produce tool-specific context files. |
54
+ | `context-budget.js` | Keep generated context within budget. |
55
+ | `design-detector.js` | Detect design-system conventions. |
56
+ | `design-spec.js` | Normalize design specifications. |
57
+ | `awesome-design.js` | Validate design guidance against awesome-design rules. |
58
+ | `browser-bridge.js` | Connect browser verification flows. |
59
+ | `agent-browser-driver.js` | Drive browser-backed agent checks. |
60
+ | `skillui-bridge.js` | Bridge skill metadata into UI surfaces. |
61
+ | `impeccable-bridge.js` | Bridge runtime checks into impeccable quality workflows. |
62
+ | `extensions.js` | Load and validate extension packs. |
63
+
64
+ ## Repository and graph helpers
65
+
66
+ | Module | Purpose |
67
+ |--------|---------|
68
+ | `code-scanner.js` | Scan source trees for routing and quality evidence. |
69
+ | `cross-artifact-impact.js` | Detect relationships between changed artifacts. |
70
+ | `cross-repo-linkage.js` | Track suite-level repository relationships. |
71
+ | `drift-detector.js` | Detect context drift between artifacts and implementation. |
72
+ | `impact.js` | Summarize expected impact of proposed changes. |
73
+ | `linkage.js` | Connect artifacts, stories, and implementation files. |
74
+ | `multi-repo-detector.js` | Detect multi-repository workspaces. |
75
+ | `reverse-sync.js` | Reflect implementation changes back into artifacts. |
76
+ | `review-required.js` | Decide when review gates should block progress. |
77
+ | `suite-state.js` | Manage state across registered project suites. |
78
+
79
+ See `../ARCHITECTURE.md` for system design and `../docs/ROADMAP.md` for planned
80
+ runtime work.
package/package.json CHANGED
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "godpowers",
3
- "version": "1.6.0",
3
+ "version": "1.6.1",
4
4
  "description": "AI-powered development system: 106 slash commands and 39 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.",
5
5
  "bin": {
6
6
  "godpowers": "./bin/install.js"
7
7
  },
8
8
  "scripts": {
9
- "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && bash scripts/smoke.sh && node scripts/test-runtime.js && node scripts/test-router.js && node scripts/test-recipes.js && node scripts/test-context-writer.js && node scripts/test-pillars.js && node scripts/test-artifact-linter.js && node scripts/test-artifact-diff.js && node scripts/test-design-foundation.js && node scripts/test-linkage.js && node scripts/test-impact.js && node scripts/test-reverse-sync.js && node scripts/test-integration.js && node scripts/test-cross-artifact.js && node scripts/test-awesome-design.js && node scripts/test-skillui-bridge.js && node scripts/test-runtime-verification.js && node scripts/test-agent-browser.js && node scripts/test-mode-d.js && node scripts/test-runtime-heuristics.js && node scripts/test-agent-validator.js && node scripts/test-story-validator.js && node scripts/test-state.js && node scripts/test-intent.js && node scripts/test-events.js && node scripts/test-golden-artifacts.js && node scripts/test-install-smoke.js && node scripts/test-checkpoint.js && node scripts/test-extensions.js && node scripts/test-event-reader.js && node scripts/test-state-lock.js && node scripts/test-cost-saver.js && node scripts/test-budget-onoff.js && node scripts/test-workflow-runner.js && node scripts/test-otel-exporter.js && node scripts/test-extensions-publish.js",
9
+ "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && bash scripts/smoke.sh && node scripts/test-runtime.js && node scripts/test-router.js && node scripts/test-recipes.js && node scripts/test-context-writer.js && node scripts/test-pillars.js && node scripts/test-artifact-linter.js && node scripts/test-artifact-diff.js && node scripts/test-design-foundation.js && node scripts/test-linkage.js && node scripts/test-impact.js && node scripts/test-reverse-sync.js && node scripts/test-integration.js && node scripts/test-cross-artifact.js && node scripts/test-awesome-design.js && node scripts/test-skillui-bridge.js && node scripts/test-runtime-verification.js && node scripts/test-agent-browser.js && node scripts/test-mode-d.js && node scripts/test-runtime-heuristics.js && node scripts/test-agent-validator.js && node scripts/test-story-validator.js && node scripts/test-state.js && node scripts/test-intent.js && node scripts/test-events.js && node scripts/test-golden-artifacts.js && node scripts/test-install-smoke.js && node scripts/test-checkpoint.js && node scripts/test-extensions.js && node scripts/test-event-reader.js && node scripts/test-state-lock.js && node scripts/test-cost-saver.js && node scripts/test-budget-onoff.js && node scripts/test-workflow-runner.js && npm run test:e2e && node scripts/test-otel-exporter.js && node scripts/test-extensions-publish.js",
10
10
  "prepublishOnly": "npm test",
11
11
  "validate-skills": "node scripts/validate-skills.js",
12
12
  "test:surface": "node scripts/test-doc-surface-counts.js",
@@ -17,7 +17,11 @@
17
17
  "test:context": "node scripts/test-context-writer.js",
18
18
  "test:pillars": "node scripts/test-pillars.js",
19
19
  "test:linter": "node scripts/test-artifact-linter.js",
20
- "test:diff": "node scripts/test-artifact-diff.js"
20
+ "test:diff": "node scripts/test-artifact-diff.js",
21
+ "test:e2e": "node tests/integration/full-arc.test.js",
22
+ "test:audit": "npm audit --omit=dev && git diff --check && npm run test:surface",
23
+ "pack:check": "node scripts/check-package-contents.js",
24
+ "release:check": "npm test && npm run test:audit && npm run pack:check"
21
25
  },
22
26
  "keywords": [
23
27
  "ai",
package/references/building/README.md CHANGED
@@ -4,14 +4,12 @@ Per-tier reference content for Tier 2 (Building: Repo, Build).
4
4
 
5
5
  ## Files
6
6
 
7
- - (placeholder)
7
+ - `BUILD-ANTIPATTERNS.md`: failure modes for implementation planning and execution.
8
+ - `BUILD-VERTICAL-SLICES.md`: guidance for slicing work into user-visible increments.
9
+ - `BUILD-WAVES.md`: dependency-aware parallelism patterns for multi-agent work.
8
10
 
9
- ## Planned content
11
+ ## Use
10
12
 
11
- - TDD violation examples with how-to-fix
12
- - Two-stage review checklists with worked findings
13
- - Vertical slice anatomy with anti-examples (horizontal "set up the database")
14
- - Atomic commit examples
15
- - Wave parallelism dependency analysis worked examples
16
-
17
- See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
13
+ Use these references when reviewing implementation plans, build execution, and
14
+ agent workstream shape. Pair them with [HAVE-NOTS.md](../HAVE-NOTS.md) for the
15
+ canonical failure-mode catalog.
package/references/planning/README.md CHANGED
@@ -4,13 +4,16 @@ Per-tier reference content for Tier 1 (Planning: PRD, Architecture, Roadmap, Sta
4
4
 
5
5
  ## Files
6
6
 
7
- - (placeholder; antipattern catalogs and worked examples to be added)
7
+ - `PRD-ANATOMY.md`: structure and evidence expectations for product requirements.
8
+ - `PRD-ANTIPATTERNS.md`: common ways PRDs become generic, untestable, or ungrounded.
9
+ - `ARCH-ANATOMY.md`: architecture decision structure, boundaries, and tradeoff framing.
10
+ - `ARCH-ANTIPATTERNS.md`: architecture theater, cargo-cult patterns, and weak constraints.
11
+ - `STACK-ANATOMY.md`: stack decision shape, flip points, and operational fit.
12
+ - `STACK-ANTIPATTERNS.md`: technology-choice failure modes and substitution-test misses.
13
+ - `ROADMAP-ANATOMY.md`: sequencing, dependency, and milestone structure.
14
+ - `ROADMAP-ANTIPATTERNS.md`: feature-factory, Gantt theater, and shelf-roadmap failures.
8
15
 
9
- ## Planned content
16
+ ## Use
10
17
 
11
- - PRD anatomy with line-by-line annotations of a substitution-tested example
12
- - ARCH antipatterns: architecture theater, paper-tiger, cargo-cult cloud-native
13
- - Worked Stack decision examples with flip-point analysis
14
- - Roadmap anti-examples: Gantt theater, feature-factory output, shelf roadmaps
15
-
16
- See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
18
+ Use these references when reviewing or generating Tier 1 artifacts. Pair them
19
+ with [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
package/references/shipping/README.md CHANGED
@@ -4,15 +4,16 @@ Per-tier reference content for Tier 3 (Deploy, Observe, Launch, Harden).
4
4
 
5
5
  ## Files
6
6
 
7
- - (placeholder)
7
+ - `DEPLOY-PATTERNS.md`: deployment promotion patterns and release safety checks.
8
+ - `DEPLOY-ANTIPATTERNS.md`: deployment failure modes and operational shortcuts.
9
+ - `OBSERVE-SLO-EXAMPLES.md`: SLO, alerting, and error-budget examples.
10
+ - `OBSERVE-ANTIPATTERNS.md`: observability gaps, noisy alerts, and weak signals.
11
+ - `LAUNCH-ANTIPATTERNS.md`: launch readiness, messaging, and adoption failure modes.
12
+ - `HARDEN-OWASP-WORKSHEETS.md`: security review worksheets based on OWASP categories.
13
+ - `HARDEN-ANTIPATTERNS.md`: hardening gaps and security theater patterns.
8
14
 
9
- ## Planned content
15
+ ## Use
10
16
 
11
- - Same-artifact promotion patterns and anti-patterns
12
- - SLO worked examples with error budget policies
13
- - Symptom-vs-cause alerting catalog
14
- - OWASP Top 10 manual review worksheets
15
- - Launch copy substitution-test calibration set
16
- - D-7 to D+7 runbook templates
17
-
18
- See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
17
+ Use these references when preparing production releases, observability plans,
18
+ launch plans, and hardening reviews. Pair them with
19
+ [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
package/skills/god-doctor.md CHANGED
@@ -48,7 +48,7 @@ GODPOWERS DOCTOR
48
48
  Install: claude (~/.claude/)
49
49
  [OK] 106 skills installed
50
50
  [OK] 39 agents installed
51
- [OK] VERSION matches (1.6.0)
51
+ [OK] VERSION matches (1.6.1)
52
52
  [WARN] routing/god-doctor.yaml exists but skill file did not until now
53
53
 
54
54
  Project: /Users/.../my-project/.godpowers/
package/skills/god-version.md CHANGED
@@ -14,7 +14,7 @@ Print version and a short capability summary.
14
14
  ## Output
15
15
 
16
16
  ```
17
- Godpowers v1.6.0
17
+ Godpowers v1.6.1
18
18
  Install: /Users/.../.claude/ (matches package.json)
19
19
  Surface: 106 skills, 39 agents, 13 workflows, 36 recipes
20
20
  Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1