godpowers 1.6.14 → 1.6.15

package/CHANGELOG.md

@@ -5,6 +5,43 @@ 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).
 
+## [1.6.15] - 2026-05-16
+
+Planning-system migration and sync-back.
+
+### Added
+- Added `lib/planning-systems.js` to detect GSD, BMAD, and Superpowers
+  planning context and convert useful signals into Godpowers prep and seed
+  artifacts.
+- Added `lib/source-sync.js` to write current Godpowers progress back into
+  managed companion files for imported planning systems.
+- Added `/god-migrate` as the explicit command for planning-system detection,
+  import, sync-back, and specialist escalation when migration evidence is
+  ambiguous.
+- Added `docs/planning-system-migration.md` with detection signals, import
+  mapping, sync-back destinations, conflict rules, and return-path guidance.
+- Added behavioral tests for GSD, BMAD, Superpowers, imported seed artifacts,
+  state recording, and idempotent sync-back.
+
+### Changed
+- `/god-init` now auto-invokes planning-system import when GSD, BMAD, or
+  Superpowers evidence is detected.
+- `/god-sync` now auto-invokes source-system sync-back when `state.json`
+  records enabled source systems.
+- `reverse-sync` now includes source-system sync-back in its runtime result.
+- `state.v1.json` now records imported source systems, import hashes,
+  sync-back hashes, conflict counts, and sync-back policy.
+
+### Guardrails
+- Imported planning context remains `[HYPOTHESIS]` until confirmed by the user
+  or a Godpowers artifact.
+- Existing Godpowers artifacts are preserved unless the user explicitly forces
+  overwrite.
+- Source-system files are not rewritten outside Godpowers-owned fences or
+  companion files.
+- Low-confidence or conflicting imports route to `god-greenfieldifier` for a
+  controlled migration plan.
+
 ## [1.6.14] - 2026-05-16
 
 Approved automation setup execution.

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-1.6.14-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-1.6.15-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.**
@@ -12,16 +12,13 @@ idea to hardened production. It runs as **slash commands inside your AI coding
 tool** (Claude Code, Codex, Cursor, etc.) that orchestrate **specialist agents**
 in fresh contexts to do the work.
 
-Version 1.6.14 builds on the executable dashboard engine and CLI status surface:
-`godpowers status --project .` and `godpowers next --project .` now compute the
-same disk-derived progress, planning visibility, proactive checks, and next
-action used by `/god-status`, `/god-next`, and God Mode closeouts.
-It adds an opt-in automation-provider layer so Godpowers can detect host
-automation surfaces such as Codex App automations, Claude Routines, Cline
-schedules, Qwen loops, Cursor Background Agents, Copilot cloud agent, and
-scriptable CLI providers without silently creating background work.
-Approved setup can now use host tool calling for simple read-only automation
-or spawn `god-automation-engineer` for complex automation setup.
+Version 1.6.15 adds planning-system migration for teams arriving from GSD,
+BMAD, or Superpowers. `/god-init` now auto-detects those systems, imports
+useful context into Godpowers prep and seed artifacts, and records source
+systems in `state.json`. `/god-sync` now syncs current Godpowers progress back
+to managed companion files so teams can return to the prior system with a clear
+handoff trail. Ambiguous imports can auto-spawn `god-greenfieldifier` for a
+controlled migration plan.
 
 It fuses four disciplines into one unified workflow:
 
@@ -147,6 +144,7 @@ npx godpowers status --project=. --json
 | `/god-status` | Re-derive state from disk | (built-in) |
 | `/god-automation-status` | Show host automation provider support | (built-in) |
 | `/god-automation-setup` | Prepare opt-in automation setup | (built-in) |
+| `/god-migrate` | Detect GSD, BMAD, and Superpowers context; import and sync back | god-greenfieldifier when needed |
 | `/god-preflight` | Read-only intake audit before project-run readiness and pillars | god-auditor |
 | `/god-audit` | Score artifacts against have-nots | god-auditor |
 | `/god-debug` | 4-phase systematic debug | god-debugger |
@@ -217,6 +215,19 @@ background agents, API triggers, or CI workflows. Safe starting templates are
 read-only status, checkpoint, review queue, hygiene, and release readiness
 reports.
 
+Godpowers can migrate from adjacent planning systems:
+
+```bash
+/god-migrate
+```
+
+This detects GSD `.planning/` or `.gsd/`, BMAD `_bmad-output/` or `.bmad/`,
+and Superpowers specs or plans. It writes
+`.godpowers/prep/IMPORTED-CONTEXT.md`, optional imported seed artifacts, and
+managed sync-back files such as `.planning/GODPOWERS-SYNC.md`,
+`_bmad-output/GODPOWERS-SYNC.md`, or
+`docs/superpowers/GODPOWERS-SYNC.md`.
+
 For existing codebases and org-constrained new projects, God Mode now runs a
 greenfield simulation audit and then actions it through a greenfieldification
 plan. It pauses before risky artifact rewrites because that process can change
@@ -339,7 +350,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 108 skills + 40 agents)](docs/reference.md)
+- [Command reference (all 109 skills + 40 agents)](docs/reference.md)
 - [Roadmap](docs/ROADMAP.md)
 - [1.5 Release Notes](RELEASE.md)
 - [Changelog](CHANGELOG.md)

package/RELEASE.md

@@ -1,21 +1,18 @@
-# Godpowers 1.6.14 Release
+# Godpowers 1.6.15 Release
 
 Date: 2026-05-16
 
-Godpowers 1.6.14 turns automation setup from a plan-only contract into an
-approved execution contract for hosts that expose tool calling. The CLI remains
-deterministic and read-only, while `/god-automation-setup` can use host-native
-tool calling for simple read-only setup or spawn `god-automation-engineer` for
-complex setup.
+Godpowers 1.6.15 adds automatic migration from GSD, BMAD, and Superpowers
+projects into Godpowers. The release also adds managed sync-back so a team can
+return to its prior planning system with current Godpowers progress visible.
 
 ## What is stable
 
-- 108 slash commands
+- 109 slash commands
 - 40 specialist agents
 - 13 executable workflows
 - 36 intent recipes
 - 15-runtime installer
-- 459 package files in the npm tarball
 - Codex installs with generated `god-*.toml` agent metadata files
 - Markdown specialist agent contracts at `<runtime>/agents/god-*.md`
 - Shared runtime bundle at `<runtime>/godpowers-runtime`
@@ -29,57 +26,68 @@ complex setup.
 
 ## What is new
 
-- Added `god-automation-engineer`.
-- Added automation execution-plan metadata to `lib/automation-providers.js`.
-- Added gated automation state recording helpers.
-- `/god-automation-setup` now shows direct host tool calling availability,
-  complex setup delegation, and the state recording path.
-- Tests now cover host tool execution plans, complex setup delegation, and
-  post-success automation recording.
-
-## Platform behavior
-
-Claude Code, Codex, Cursor, Windsurf, Gemini, OpenCode, Copilot, Augment,
-Trae, Cline, Kilo, Antigravity, Qwen, CodeBuddy, and Pi all receive the same
-portable Markdown agent contracts. Codex also receives `god-*.toml` files as
-its registry adapter.
-
-The dashboard and automation provider engines ship in the installed runtime
-bundle so host tools can use shared implementation code instead of parallel
-command-specific Markdown contracts. If a host platform cannot provide a true
-fresh-context agent spawn, durable scheduler, or callable automation tool,
-Godpowers must say so visibly and report the work as local runtime only,
-manual workflow only, or simulated in current context.
-
-## Safety policy
-
-Godpowers may proactively suggest next steps and may run directly evidenced
-local helpers. It may spawn bounded agents only when the current workflow owns
-that surface.
-
-Godpowers still must not auto-run these without explicit user intent:
-
-- deployed staging verification against a guessed URL
-- production launch
-- provider dashboard, admin console, DNS, credential, or secret checks
-- schedule, routine, background agent, API trigger, or CI workflow creation
-- broad dependency upgrades
-- destructive repair, rollback, reset, delete, or cleanup
-- clearing `.godpowers/REVIEW-REQUIRED.md`
-- accepting Critical security findings
-- git stage, commit, push, package, release, or publish
-- `.godpowers/automations.json` writes before host setup success
+- Added `lib/planning-systems.js` for GSD, BMAD, and Superpowers detection.
+- Added `lib/source-sync.js` for managed sync-back companion files.
+- Added `/god-migrate` as the explicit migration command.
+- `/god-init` now auto-invokes planning-system import when source systems are
+  detected.
+- `/god-sync` now auto-invokes source-system sync-back when enabled source
+  systems are recorded in `state.json`.
+- `reverse-sync` now returns source-system sync-back results.
+- `state.v1.json` now records source-system import and sync-back state.
+- Added `docs/planning-system-migration.md`.
+
+## Migration behavior
+
+Godpowers detects:
+
+- GSD: `.planning/`, `.gsd/`, `GSD.md`, and `gsd*.md`
+- BMAD: `_bmad/`, `_bmad-output/`, `.bmad-core/`, `.bmad/`, and `BMAD.md`
+- Superpowers: `docs/superpowers/`, `.superpowers/`, `SUPERPOWERS.md`, and
+  project-local skills
+
+Imported context is written to `.godpowers/prep/IMPORTED-CONTEXT.md`.
+Missing Godpowers seed artifacts are created only when source evidence exists.
+Existing Godpowers artifacts are preserved unless the user explicitly forces an
+overwrite.
+
+## Sync-back behavior
+
+Godpowers writes managed companion files:
+
+- GSD: `.planning/GODPOWERS-SYNC.md` or `.gsd/GODPOWERS-SYNC.md`
+- BMAD: `_bmad-output/GODPOWERS-SYNC.md` or `.bmad/GODPOWERS-SYNC.md`
+- Superpowers: `docs/superpowers/GODPOWERS-SYNC.md` or
+  `.superpowers/GODPOWERS-SYNC.md`
+
+Pointer fences are written only when a safe native state file already exists.
+Godpowers never rewrites source-system prose outside managed fences.
+
+## Auto-invoke and auto-spawn policy
+
+The import path is local runtime work and must be reported as:
+
+```
+Agent: none, local runtime only
+```
+
+The sync-back path is also local runtime work and must be reported the same
+way.
+
+Godpowers spawns `god-greenfieldifier` only when import confidence is low,
+multiple source systems conflict, or canonical seed artifacts cannot be safely
+created from available evidence.
 
 ## Validation
 
 Release validation includes:
 
-- `node scripts/test-dashboard.js`
-- `node scripts/test-automation-providers.js`
+- `node scripts/test-planning-systems.js`
+- `node scripts/test-reverse-sync.js`
 - `npm test`
 - `npm run test:audit`
 - `node scripts/check-package-contents.js`
 - `git diff --check`
 
-The `v1.6.14` git tag points to the release commit that matches the npm
-`godpowers@1.6.14` package.
+The `v1.6.15` git tag points to the release commit that matches the npm
+`godpowers@1.6.15` package.

package/SKILL.md

@@ -214,7 +214,7 @@ Auto-invoked:
   Trigger: <what caused this automatic step>
   Agent: <god-updater | god-context-writer | none, local runtime only>
   Local syncs:
-    + <reverse-sync | pillars-sync | checkpoint-sync | context-refresh>: <result or skipped reason>
+    + <planning-system-import | reverse-sync | source-sync | pillars-sync | checkpoint-sync | context-refresh>: <result or skipped reason>
   Artifacts: <changed files, no-op, or deferred>
   Log: <SYNC-LOG.md, CHECKPOINT.md, REVIEW-REQUIRED.md, or none>
 ```
@@ -238,6 +238,8 @@ Automatic steps that especially need visible reporting:
 - checkpoint refresh after state mutations
 - automation provider detection in `/god-status`, `/god-next`,
   `/god-automation-status`, and `/god-automation-setup`
+- planning-system import during `/god-init` or `/god-migrate`
+- source-system sync-back during `/god-sync`, `/god-scan`, or `/god-migrate`
 
 ### 13. Proactive Auto-Invoke Policy
 Godpowers should be proactive from disk evidence, not from guesswork. Before
@@ -265,6 +267,11 @@ Run these local runtime helpers automatically when their trigger is present:
   `PROGRESS.md` mutation.
 - Lightweight reverse-sync or linkage scan after code or artifact edits.
 - Pillars sync planning after durable artifact truth changes.
+- `lib/planning-systems.importPlanningContext` when GSD, BMAD, or
+  Superpowers planning context is detected during `/god-init` or
+  `/god-migrate`.
+- `lib/source-sync.run` when `state.json` records enabled `source-systems`
+  entries and `/god-sync`, `/god-scan`, or `/god-migrate` closes a workflow.
 - Context refresh dry-run after `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`,
   `.cursor/rules/`, `.windsurfrules`, `.github/copilot-instructions.md`,
   `.clinerules`, `.roo/`, or `.continue/` changes.
@@ -289,6 +296,9 @@ Spawn these agents only when the trigger is direct and scope is bounded:
 - `god-automation-engineer` after the user approves provider, template,
   cadence, and scope for multi-template, write-capable, background-agent,
   scriptable-scheduler, or provider-uncertain automation setup.
+- `god-greenfieldifier` when imported GSD, BMAD, or Superpowers context has
+  low confidence, conflicting systems, or missing canonical Godpowers seed
+  artifacts after local import.
 
 #### Level 4: Explicit approval required
 Never auto-run these from inference alone: