godpowers 0.15.6 → 0.15.7

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.7] - 2026-05-11
+
+Planning import release. Lets `/god-init` preserve useful context from nearby
+planning systems without making those systems authoritative.
+
+### Added
+- `/god-init` now detects GSD, Superpowers, BMAD, and similar planning context
+  during project preparation.
+- Added `.godpowers/prep/IMPORTED-CONTEXT.md` as a non-authoritative
+  preparation artifact for imported product, delivery, architecture, and stack
+  signals.
+- PRD, architecture, roadmap, and stack agents now read imported context when
+  present and treat it as hypothesis-level supporting evidence.
+
 ## [0.15.6] - 2026-05-11
 
 Quiet init release. Keeps `/god-init` focused on the next useful command while

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.6-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.7-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.**

package/agents/god-architect.md

@@ -19,6 +19,21 @@ flip points.
 Before starting:
 - `.godpowers/prd/PRD.md` MUST exist
 - PRD MUST pass have-nots (run god-auditor first if uncertain)
+- Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
+  context.
+
+## Imported Preparation Context
+
+If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read its technical signals
+before drafting ARCH. Use imported architecture, integration, risk, and stack
+constraints as hypothesis-level input only.
+
+Rules:
+- Do not let imported context override PRD NFRs or Godpowers state.
+- Convert useful imported signals into ADR context, tradeoffs, or open
+  questions.
+- If imported context conflicts with the PRD, the PRD wins and the conflict
+  becomes an `[OPEN QUESTION]`.
 
 ## Output
 

package/agents/god-orchestrator.md

@@ -30,7 +30,8 @@ You and only you are responsible for:
 2. **Calling the play** - selecting the next specialist agent for each tier
    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.
+   `intent.yaml`, `.godpowers/prep/IMPORTED-CONTEXT.md`, and `events.jsonl`
+   originate from you or agents you spawn.
 4. **Audibles** - handling pause checkpoints, the critical-finding gate, and
    the --yolo carve-out when the user has authorized auto-resolve.
 5. **Clock management** - mandatory final sync after Tier 3 (always, including
@@ -138,6 +139,35 @@ Before each tier, check whether this repo is part of a registered suite:
 3. Per-repo state.json remains the source of truth; never write to
    `.godpowers/suite/` directly (that's god-coordinator's surface).
 
+## Planning-system context import
+
+During `/god-init`, scan for adjacent methodology artifacts from GSD,
+Superpowers, BMAD, and similar systems. Treat them as preparation context,
+not as source of truth.
+
+Detection signals:
+- GSD: `.gsd/`, `.planning/`, `GSD.md`, `gsd*.md`
+- Superpowers: `.superpowers/`, `superpowers/`, `SUPERPOWERS.md`,
+  `.claude/skills/`, `.codex/skills/`
+- BMAD: `.bmad-core/`, `bmad-core/`, `.bmad/`, `BMAD.md`,
+  `docs/prd.md`, `docs/architecture.md`, `docs/roadmap.md`
+
+When signals are found:
+1. Read only likely planning files, not dependency folders or generated build
+   output.
+2. Summarize product, delivery, technical, risk, and already-built signals into
+   `.godpowers/prep/IMPORTED-CONTEXT.md` using `templates/IMPORTED-CONTEXT.md`.
+3. Label every imported claim as `[HYPOTHESIS]` unless the user directly stated
+   it during this session.
+4. Record source paths and confidence so downstream agents can decide how much
+   weight to give each signal.
+5. If imported context conflicts with Godpowers state, user intent, or a
+   completed Godpowers artifact, keep the Godpowers artifact as authoritative
+   and add an `[OPEN QUESTION]` to imported context.
+
+Downstream planning agents may read this artifact. They must cite it as
+supporting evidence only.
+
 ## Routing-Driven Decisions
 
 For routing decisions, consult `<runtimeRoot>/routing/<command>.yaml` files.

package/agents/god-pm.md

@@ -29,6 +29,22 @@ required sections:
 7. **Appetite** (time/resource/technical constraints)
 8. **Open Questions** (with owner and due date)
 
+## Imported Preparation Context
+
+If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read it before drafting the
+PRD. Use product signals from GSD, Superpowers, BMAD, or similar systems as
+hypothesis-level input only.
+
+Rules:
+- Do not copy imported text wholesale into the PRD.
+- Do not treat imported context as source of truth.
+- Convert relevant imported product signals into `[HYPOTHESIS]` requirements,
+  success metrics, scope notes, no-gos, or open questions.
+- If imported context conflicts with user intent or existing Godpowers state,
+  preserve the Godpowers state and add an `[OPEN QUESTION]`.
+- In PRD rationale, mention the source only when it materially changes a
+  requirement.
+
 ## Quality Gates
 
 Run these checks on every section before declaring done:

package/agents/god-roadmapper.md

@@ -16,6 +16,22 @@ Sequence the work.
 ## Gate Check
 
 `.godpowers/arch/ARCH.md` MUST exist and pass have-nots.
+Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
+context.
+
+## Imported Preparation Context
+
+If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read its delivery signals
+before sequencing milestones. Use imported GSD, Superpowers, BMAD, or similar
+stories and plans as hypothesis-level input only.
+
+Rules:
+- Do not add roadmap features that are not grounded in the PRD.
+- Use imported milestones, stories, and done-work signals to inform ordering,
+  dependency edges, and open questions.
+- If imported context conflicts with PRD or ARCH, PRD and ARCH win.
+- Mark any imported sequencing assumption as `[HYPOTHESIS]` until confirmed by
+  Godpowers artifacts or the user.
 
 ## Process
 

package/agents/god-stack-selector.md

@@ -15,6 +15,20 @@ Pick the technology stack.
 ## Gate Check
 
 `.godpowers/arch/ARCH.md` MUST exist.
+Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
+context.
+
+## Imported Preparation Context
+
+If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read its technical and stack
+signals before scoring candidates. Use imported technology choices, constraints,
+and team familiarity as hypothesis-level input only.
+
+Rules:
+- Do not let imported stack preference override ARCH NFRs or ADRs.
+- Treat imported technology choices as candidate evidence, not decisions.
+- If imported context conflicts with ARCH, ARCH wins and the conflict becomes a
+  stack open question.
 
 ## Process
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.6",
+  "version": "0.15.7",
   "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/routing/god-arch.yaml

@@ -19,6 +19,7 @@ execution:
   context: fresh
   reads:
     - .godpowers/prd/PRD.md
+    - .godpowers/prep/IMPORTED-CONTEXT.md
     - templates/ARCH.md
   writes:
     - .godpowers/arch/ARCH.md

package/routing/god-init.yaml

@@ -19,6 +19,7 @@ execution:
     - .godpowers/PROGRESS.md
     - .godpowers/state.json
     - .godpowers/intent.yaml
+    - .godpowers/prep/IMPORTED-CONTEXT.md
 
 success-path:
   next-recommended: /god-prd

package/routing/god-prd.yaml

@@ -21,6 +21,7 @@ execution:
   context: fresh
   reads:
     - .godpowers/intent.yaml
+    - .godpowers/prep/IMPORTED-CONTEXT.md
     - templates/PRD.md
   writes:
     - .godpowers/prd/PRD.md

package/routing/god-roadmap.yaml

@@ -17,6 +17,7 @@ execution:
   reads:
     - .godpowers/prd/PRD.md
     - .godpowers/arch/ARCH.md
+    - .godpowers/prep/IMPORTED-CONTEXT.md
     - templates/ROADMAP.md
   writes:
     - .godpowers/roadmap/ROADMAP.md

package/routing/god-stack.yaml

@@ -14,6 +14,9 @@ prerequisites:
 execution:
   spawns: [god-stack-selector]
   context: fresh
+  reads:
+    - .godpowers/arch/ARCH.md
+    - .godpowers/prep/IMPORTED-CONTEXT.md
   writes:
     - .godpowers/stack/DECISION.md
 

package/skills/god-init.md

@@ -30,6 +30,15 @@ needs to specify a mode.
    - Look for org-level context (current dir + parent dirs):
      - .godpowers/org-context.yaml
      - Workspace configs that share standards
+   - Look for adjacent planning-system context:
+     - GSD: `.gsd/`, `.planning/`, `GSD.md`, `gsd*.md`
+     - Superpowers: `.superpowers/`, `superpowers/`, `SUPERPOWERS.md`,
+       `.claude/skills/`, `.codex/skills/`
+     - BMAD: `.bmad-core/`, `bmad-core/`, `.bmad/`, `BMAD.md`,
+       `docs/prd.md`, `docs/architecture.md`, `docs/roadmap.md`
+   - If any are detected, summarize useful signals into
+     `.godpowers/prep/IMPORTED-CONTEXT.md` as preparation context.
+     Do not treat external planning-system files as source of truth.
 
 3. **Announce findings in plain English** (no jargon):
    - Empty dir + no org context: "Detected: empty directory. Starting fresh."
@@ -48,6 +57,8 @@ needs to specify a mode.
    The orchestrator will:
    - Run Mode Detection (announced in plain English; stored as A/B/C/E internally)
    - Run Scale Detection (trivial/small/medium/large/enterprise)
+   - Run planning-system context detection for GSD, Superpowers, and BMAD
+   - Write `.godpowers/prep/IMPORTED-CONTEXT.md` when useful context exists
    - For brownfield: schedule archaeology + reconstruction as preflight
    - For bluefield: load org-context as constraint
    - Create directory structure
@@ -65,6 +76,8 @@ needs to specify a mode.
    ```
    .godpowers/
      PROGRESS.md
+     prep/
+       IMPORTED-CONTEXT.md   # only when GSD / Superpowers / BMAD context exists
      prd/
      arch/
        adr/
@@ -99,6 +112,11 @@ needs to specify a mode.
 
 `.godpowers/PROGRESS.md` created with initial state.
 
+If GSD, Superpowers, BMAD, or similar planning context is detected, create
+`.godpowers/prep/IMPORTED-CONTEXT.md`. This artifact is preparation context,
+not source of truth. It feeds PRD, architecture, roadmap, and stack decisions
+as hypothesis-level input only.
+
 ## AI-tool context (automatic for explicit init)
 
 After PROGRESS.md is written, decide from the trigger phrase:

package/templates/IMPORTED-CONTEXT.md

@@ -0,0 +1,40 @@
+# Imported Preparation Context
+
+> This artifact captures non-authoritative context imported from adjacent
+> planning systems. Godpowers artifacts remain the source of truth after they
+> are created.
+
+## Sources Detected
+
+- [DECISION] Source system: [GSD / Superpowers / BMAD / other].
+- [DECISION] Source path: [relative path].
+- [HYPOTHESIS] Useful signal: [what this source appears to clarify].
+- [HYPOTHESIS] Confidence: [high / medium / low] because [brief reason].
+
+## Product Signals For PRD
+
+- [HYPOTHESIS] User or persona signal: [imported detail].
+- [HYPOTHESIS] Problem or outcome signal: [imported detail].
+- [HYPOTHESIS] Scope or no-go signal: [imported detail].
+- [OPEN QUESTION] Imported product ambiguity: [question] -- Owner: user -- Due: before /god-prd.
+
+## Delivery Signals For Roadmap
+
+- [HYPOTHESIS] Existing milestone or story signal: [imported detail].
+- [HYPOTHESIS] Dependency or sequencing signal: [imported detail].
+- [HYPOTHESIS] Done or already-built signal: [imported detail].
+- [OPEN QUESTION] Imported delivery ambiguity: [question] -- Owner: user -- Due: before /god-roadmap.
+
+## Technical Signals For Architecture And Stack
+
+- [HYPOTHESIS] Architecture or integration signal: [imported detail].
+- [HYPOTHESIS] Technology or constraint signal: [imported detail].
+- [HYPOTHESIS] Risk or compliance signal: [imported detail].
+- [OPEN QUESTION] Imported technical ambiguity: [question] -- Owner: user -- Due: before /god-arch.
+
+## Use Rules
+
+- [DECISION] Godpowers agents may use this artifact as preparation context only.
+- [DECISION] This artifact must not override `.godpowers/intent.yaml`, `.godpowers/state.json`, `PROGRESS.md`, or any completed Godpowers artifact.
+- [DECISION] If imported context conflicts with user intent or a Godpowers artifact, the Godpowers artifact wins and the conflict becomes an open question.
+- [DECISION] PRD, architecture, roadmap, and stack agents should cite imported signals as `[HYPOTHESIS]` until confirmed by Godpowers artifacts or the user.