godpowers 0.15.10 → 0.15.11

package/CHANGELOG.md

@@ -5,6 +5,18 @@ 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.11] - 2026-05-11
+
+God Mode resume release. Fixes `/god-mode --yolo` prompting for a project
+description when durable Godpowers state already exists.
+
+### Changed
+- `/god-mode` now treats existing `.godpowers` state as a resume signal and
+  rehydrates intent from checkpoint, state, progress, intent, prep, and tier
+  artifacts before asking the user anything.
+- The orchestrator now documents that asking "what do you want to build?" in a
+  brownfield repo with existing Godpowers artifacts is a routing bug.
+
 ## [0.15.10] - 2026-05-11
 
 God Mode continuity release. Makes red verification output repair work inside

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.10-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.11-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.**
@@ -153,6 +153,9 @@ going through build, verification, repair, launch, and final sync. Red tests,
 typecheck, lint, build, or check output enter the repair loop instead of being
 reported as the final result.
 
+If `.godpowers` state already exists, `/god-mode --yolo` resumes from disk
+instead of asking for the project description again.
+
 ## Architecture
 
 ### Slash Command + Specialist Agent Pattern

package/agents/god-orchestrator.md

@@ -567,10 +567,19 @@ Default: If you say "go", I'll pick [X] because [Y].
 ## Resume Protocol
 
 On every invocation:
-1. Read PROGRESS.md from disk (NEVER trust conversation memory)
-2. Scan ALL artifact paths to verify what actually exists
-3. If PROGRESS.md and disk disagree: disk wins. Repair PROGRESS.md.
-4. Continue from the first non-done sub-step
+1. Read `.godpowers/CHECKPOINT.md`, `.godpowers/state.json`,
+   `.godpowers/PROGRESS.md`, and `.godpowers/intent.yaml` from disk. NEVER
+   trust conversation memory.
+2. Scan ALL artifact paths to verify what actually exists.
+3. If durable state exists, do not ask the user to describe the project again.
+   Reconstruct intent from disk and continue.
+4. If PROGRESS.md and disk disagree: disk wins. Repair PROGRESS.md.
+5. Continue from the first non-done sub-step or the first red verification
+   step.
+
+Only ask "what do you want to build?" when no `.godpowers` state, no intent,
+no checkpoint, and no completed artifact exists. In a brownfield repo with
+existing Godpowers artifacts, asking that question is a routing bug.
 
 ## Mode Detection (Tier 0 setup)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.10",
+  "version": "0.15.11",
   "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-mode.md

@@ -16,7 +16,15 @@ You are receiving a /god-mode invocation. Your job is to spawn the
 
 ## Process
 
-1. Greet the user briefly: "God Mode engaged. Describe what you want to build."
+1. Resolve whether this is a new arc or a resume:
+   - If `.godpowers/state.json`, `.godpowers/PROGRESS.md`, or
+     `.godpowers/CHECKPOINT.md` exists, this is a resume. Do not ask the user
+     to describe the project again. Rehydrate intent from disk and continue.
+   - If no durable Godpowers state exists and no project description was
+     supplied in the invocation, greet briefly: "God Mode engaged. Describe
+     what you want to build."
+   - If no durable state exists and the invocation includes a description, use
+     that description immediately.
 
 2. **Auto-detect project type in background** (no jargon to user):
    - Scan working directory for code presence (package.json, src/, etc.)
@@ -25,7 +33,22 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - Announce in plain English what was detected (see god-orchestrator
      "How to announce" section)
 
-3. Wait for the user's project description (any format).
+3. Load durable resume context before asking anything:
+   - `.godpowers/CHECKPOINT.md` first, when present
+   - `.godpowers/state.json`
+   - `.godpowers/PROGRESS.md`
+   - `.godpowers/intent.yaml`, when present
+   - `.godpowers/prep/INITIAL-FINDINGS.md`, when present
+   - `.godpowers/prep/IMPORTED-CONTEXT.md`, when present
+   - Existing tier artifacts on disk
+
+   If these files contain enough information to identify the project and next
+   unfinished or red step, continue automatically. If the only missing data is
+   a nice-to-have description, use a `[HYPOTHESIS]` from existing artifacts and
+   keep moving.
+
+   Ask for a description only when there is no durable intent, no completed
+   artifact, and no resumable state.
 
 4. Parse flags from the invocation:
    - `--yolo` (skip pauses, pick defaults)
@@ -43,9 +66,10 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - `--greenfield` (force greenfield, skip archaeology even if code exists)
 
 5. Spawn the **god-orchestrator** agent via Task tool with:
-   - The user's project description
+   - The user's project description, or durable intent recovered from disk
    - The detected mode (A/B/C/E)
    - The active flags
+   - Instruction that existing `.godpowers` state means resume, not prompt
    - Instruction to read `.godpowers/PROGRESS.md` from disk if it exists
    - Instruction to read `.godpowers/prep/INITIAL-FINDINGS.md` and
      `.godpowers/prep/IMPORTED-CONTEXT.md` if present before choosing the