godpowers 0.15.8 → 0.15.10

package/CHANGELOG.md

@@ -5,6 +5,37 @@ 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.10] - 2026-05-11
+
+God Mode continuity release. Makes red verification output repair work inside
+the same autonomous arc instead of a terminal summary.
+
+### Changed
+- `/god-mode` now treats failed tests, lint, typecheck, build, or check commands
+  as repairable work and enters an autonomous repair loop before declaring the
+  arc complete.
+- Build completion now requires test, lint, and typecheck/check commands to be
+  green when those commands exist.
+- `/god-mode --yolo` now auto-runs repair loops, with Critical security findings
+  remaining the only unconditional pause.
+- Roadmap and build planning language now uses Godpowers delivery increments
+  instead of preserving imported methodology terminology.
+
+## [0.15.9] - 2026-05-11
+
+Early design planning release. Lets UI and product-experience projects shape
+DESIGN.md before architecture.
+
+### Changed
+- `/god-init` now records UI and product-experience signals in
+  `.godpowers/prep/INITIAL-FINDINGS.md`.
+- `/god-prd`, `/god-next`, and `/god-mode` now route to `/god-design` after
+  PRD and before `/god-arch` when UI or product-experience signals are found.
+- `/god-design` now requires PRD, not stack, so DESIGN.md can inform
+  architecture, roadmap, and stack instead of arriving after them.
+- Architecture, roadmap, and stack routing and agents now read DESIGN.md and
+  PRODUCT.md when present.
+
 ## [0.15.8] - 2026-05-11
 
 Init preparation release. Documents what Godpowers found before PRD, next-step

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.8-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.10-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.**
@@ -75,6 +75,12 @@ PRD complete: .godpowers/prd/PRD.md
 Suggested next: /god-arch (design the architecture)
 ```
 
+For UI or product-experience projects, PRD can route to design first:
+
+```
+Suggested next: /god-design (shape product experience)
+```
+
 You can also ask any time:
 
 ```
@@ -135,13 +141,18 @@ For real-world scenarios beyond greenfield:
 
 ```
 /god-mode                # Standard: pauses for real questions only
-/god-mode --yolo         # Zero pauses. Picks every default. Full send.
+/god-mode --yolo         # Zero pauses except Critical security. Repairs red checks before it stops.
 /god-mode --conservative # More checkpoints
 /god-mode --from=arch    # Resume from a specific tier
 /god-mode --audit        # Score existing artifacts. Build nothing.
 /god-mode --dry-run      # Plan everything. Build nothing.
 ```
 
+`/god-mode` is not complete when it merely writes planning artifacts. It keeps
+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.
+
 ## Architecture
 
 ### Slash Command + Specialist Agent Pattern
@@ -164,7 +175,7 @@ Skill updates:   PROGRESS.md
 | Tier | Sub-steps | Specialists |
 |------|-----------|-------------|
 | 0: Orchestration | mode detection, scale, progress | god-orchestrator |
-| 1: Planning | PRD, ARCH, ROADMAP, STACK | god-pm, god-architect, god-roadmapper, god-stack-selector |
+| 1: Planning | PRD, optional DESIGN, ARCH, ROADMAP, STACK | god-pm, god-designer, god-architect, god-roadmapper, god-stack-selector |
 | 2: Building | repo, plan, execute, review | god-repo-scaffolder, god-planner, god-executor, god-spec-reviewer, god-quality-reviewer |
 | 3: Shipping | deploy, observe, launch, harden | god-deploy-engineer, god-observability-engineer, god-launch-strategist, god-harden-auditor |
 

package/agents/god-architect.md

@@ -23,6 +23,9 @@ Before starting:
   context.
 - Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
   context.
+- Optional: `.godpowers/design/DESIGN.md` and
+  `.godpowers/design/PRODUCT.md` may exist as early product-experience
+  preparation.
 
 ## Imported Preparation Context
 
@@ -34,10 +37,17 @@ 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.
 
+If `.godpowers/design/DESIGN.md` or `.godpowers/design/PRODUCT.md` exists,
+read them before drafting ARCH. Use early design to identify user-facing
+surfaces, routes, component boundaries, state flows, accessibility needs, and
+where architecture must preserve product experience.
+
 Rules:
 - Do not let imported context override PRD NFRs or Godpowers state.
 - Convert useful imported signals into ADR context, tradeoffs, or open
   questions.
+- Convert useful design signals into containers, ADR context, UI boundary
+  descriptions, or open questions.
 - If imported context conflicts with the PRD, the PRD wins and the conflict
   becomes an `[OPEN QUESTION]`.
 

package/agents/god-designer.md

@@ -4,7 +4,7 @@ description: |
   Lifecycle owner of DESIGN.md and PRODUCT.md. Detects impeccable; if
   installed, delegates to /impeccable teach (initial) or /impeccable
   document (refresh from code). If not installed, falls back to a
-  minimal builder using PRD/ARCH/STACK.
+  minimal builder using prep artifacts, PRD, and any available ARCH/STACK.
 
   Spawned by: /god-design, god-orchestrator (Tier 1, conditional on UI)
 tools: Read, Write, Edit, Bash, Grep, Glob
@@ -78,10 +78,18 @@ Cascade:
   - `references/design/UX-WRITING.md` (copy)
   - `references/design/DESIGN-ANTIPATTERNS.md` (what to avoid)
 
-  Use PRD.md (target users, register hints), ARCH.md (UI surface),
-  STACK.md (UI framework) to generate a starter DESIGN.md from the
-  template, applying the rules from the references above. The output
-  will be less polished than impeccable's, but it's not toothless: the
+  Read `.godpowers/prep/INITIAL-FINDINGS.md` and
+  `.godpowers/prep/IMPORTED-CONTEXT.md` when present, then use PRD.md
+  (target users, flows, register hints), plus ARCH.md and STACK.md only
+  when they already exist. Early mode runs after PRD and before
+  architecture, so do not require ARCH or STACK. In early mode, produce
+  an experience contract that architecture and stack can honor later:
+  screens, flows, component needs, interaction states, product voice,
+  constraints, anti-references, and visual token direction.
+
+  Generate a starter DESIGN.md from the template, applying the rules
+  from the references above. The output will be less polished than
+  impeccable's, but it's not toothless: the
   references encode our design opinions across all 7 domains
   (typography, color, spatial, motion, interaction, responsive,
   ux-writing) at shallower depth than impeccable's full skill set.
@@ -152,7 +160,8 @@ After done, return to god-orchestrator with:
 - DESIGN.md path
 - PRODUCT.md path (if produced)
 - Validation summary (errors, warnings)
-- Suggested next: `/god-repo` (proceed to scaffolding)
+- Suggested next: `/god-arch` when design ran early, or `/god-repo` when
+  architecture, roadmap, and stack are already complete
 
 ## Linkage hooks
 

package/agents/god-executor.md

@@ -20,6 +20,8 @@ You receive:
 - Relevant ARCH context (only what's needed for this slice)
 - Stack DECISION (tooling)
 - The slice's dependencies (what must already exist)
+- Optional repair payload: failing command, error counts, focused diagnostics,
+  and files implicated by a previous verification run
 
 ## TDD Sequence (mandatory)
 
@@ -54,10 +56,12 @@ For every behavior in this slice:
 
 1. Run the full test suite. All tests must pass.
 2. Run the linter. All warnings resolved.
-3. Stage your changes.
-4. Return control to orchestrator with:
+3. Run typecheck/check command when present. All errors resolved.
+4. Stage your changes.
+5. Return control to orchestrator with:
    - Summary of what was implemented
    - Test results
+   - Typecheck/check results
    - Files changed
    - Ready for two-stage review
 
@@ -73,4 +77,13 @@ happen.
 - Multiple slices touched in one execution
 - Linter warnings unresolved
 - Test suite failing (any test, not just yours)
+- Typecheck/check command failing
 - Stub/placeholder code in the implementation
+
+## Repair Mode
+
+If invoked with a repair payload, stay narrowly focused on the failing command.
+Do not reopen PRD, ARCH, roadmap, or stack unless the diagnostic proves the
+artifact is stale. Fix code, config, imports, tests, generated types, or
+tooling until the command passes. If the same root failure survives 3 focused
+attempts, return the smallest human-only question needed to continue.

package/agents/god-orchestrator.md

@@ -227,18 +227,23 @@ This is the third layer of decision support:
 
 ## Detection-Driven Tier 1 Routing
 
-After STACK done, branch on UI presence:
+After PRD and before ARCH, branch on UI or product-experience presence:
 
 1. Call `lib/design-detector.isUiProject(projectRoot)` to determine
    whether DESIGN tier is required.
 2. Call `lib/design-detector.isImpeccableInstalled(projectRoot)` to
    determine whether to delegate or fall back.
-3. Persist results to `state.json.project.detection-results`.
-4. If `requires-design: true`: spawn `god-designer` for DESIGN tier
-   (Tier 1 sub-step 5). god-designer delegates to impeccable's
+3. Read `.godpowers/prep/INITIAL-FINDINGS.md`,
+   `.godpowers/prep/IMPORTED-CONTEXT.md`, and `.godpowers/prd/PRD.md`
+   for UI, workflow, journey, component, brand, accessibility, and screen
+   signals.
+4. Persist results to `state.json.project.detection-results`.
+5. If `requires-design: true`: spawn `god-designer` for DESIGN tier before
+   architecture. god-designer delegates to impeccable's
    `/impeccable teach` if available, else falls back to a minimal builder.
-5. If `requires-design: false`: mark `tier-1.design.status = not-required`
-   and `tier-1.product.status = not-required`. Advance to Tier 2.
+   DESIGN.md and PRODUCT.md then inform architecture, roadmap, and stack.
+6. If `requires-design: false`: mark `tier-1.design.status = not-required`
+   and `tier-1.product.status = not-required`. Continue to architecture.
 
 ## Linkage and Reverse-Sync
 
@@ -272,17 +277,52 @@ last known hash in state.json:
 
 ## Extended Critical-Finding Gate
 
-The existing critical-finding gate now also fires on:
-- Breaking drift findings (e.g., WCAG contrast fail, ARCH container
-  responsibility violation, STACK dep version mismatch)
-- Critical impeccable findings on the diff
-- Lint errors from `lib/artifact-linter` on any artifact
-- Validator errors from `lib/have-nots-validator`
+The critical-finding gate fires on:
+- Critical security findings from god-harden-auditor
 - god-design-reviewer BLOCK verdicts
-
-All pause both default mode AND --yolo. Lint errors cannot be
-auto-resolved; they're mechanical signal that something is structurally
-wrong.
+- Breaking drift findings that would make already-written artifacts unsafe
+  to trust without human context
+- Artifact linter or have-nots errors that still fail after repair attempts
+
+Only Critical security findings always pause, including under --yolo.
+Everything else must first enter the autonomous repair loop below. A failed
+typecheck, lint, check, unit test, generated artifact lint, or have-nots pass is
+not a reason to declare the arc complete. It is work.
+
+## Autonomous Repair Loop
+
+Godpowers full-arc means: plan, build, verify, repair, ship, sync. Do not stop
+at "artifacts generated" when the repo is still red.
+
+When any mechanical verification fails:
+- tests, typecheck, lint, formatter, build, `bun run check`, `npm run check`,
+  `npm test`, `cargo test`, `go test`, or equivalent
+- artifact lint or have-nots validation
+- generated scaffold audit with fixable failures
+- launch smoke check with deterministic reproduction
+
+Do this:
+1. Record the exact failing command, counts, and highest-signal diagnostics in
+   `.godpowers/build/STATE.md` or the active tier state file.
+2. Classify the failure:
+   - `repairable`: code, config, type, lint, test, generated artifact, missing
+     dependency, bad scaffold, or stale state problem.
+   - `human-only`: product scope contradiction, credential missing, paid vendor
+     decision, legal/compliance choice, or Critical security acceptance.
+3. For `repairable`, spawn the owning agent again in repair mode with only the
+   failing diagnostics, touched files, relevant artifact excerpts, and the
+   command to re-run.
+4. Re-run the failing command after each repair attempt.
+5. Repeat until green or until the same root failure survives 3 repair attempts.
+6. If repair succeeds, continue the same `/god-mode` run. Do not hand off a
+   "next recommended delivery increment" while required verification is red.
+7. If the same root failure survives 3 attempts, pause with a precise blocker,
+   attempted fixes, and the smallest human question needed to continue.
+
+Under `--yolo`, the repair loop auto-runs. It may commit atomic repair commits
+after tests pass. If a git remote exists and the user passed an explicit push
+flag or the project intent says pushing is allowed, push after the green commit
+and then continue the arc. Pushing is not a terminal state.
 
 ## YOLO Behavior with Design + Linkage
 
@@ -292,7 +332,8 @@ wrong.
 | Impeccable install prompt | Pause | Auto-yes; log |
 | PRODUCT.md interview | Pause | Pause anyway (load-bearing brand) |
 | Design token defaults | Pause | Auto-pick impeccable defaults; log |
-| Lint errors | Pause | Pause anyway |
+| Repairable mechanical failures | Repair loop | Repair loop |
+| Lint errors after 3 repair attempts | Pause | Pause with diagnostics |
 | Lint warnings | Continue, log | Continue, log |
 | Drift (informational) | Continue | Continue |
 | Drift (breaking) | Pause | Pause anyway |
@@ -312,8 +353,9 @@ wrong.
 5. Verify their output exists on disk
 6. Run have-nots check on the artifact
 7. If pass: update PROGRESS.md, move to next sub-step
-8. If fail: spawn the agent again with the failures, OR pause for human
-9. Repeat until all tiers complete
+8. If fail and repairable: enter the autonomous repair loop
+9. If fail and human-only: pause with the smallest needed question
+10. Repeat until all tiers complete and verification is green
 ```
 
 ## Specialist Agent Routing
@@ -323,9 +365,10 @@ For single-agent sub-steps:
 | Sub-step | Spawn Agent | Reads | Writes |
 |----------|-------------|-------|--------|
 | PRD | god-pm | user intent | .godpowers/prd/PRD.md |
-| Architecture | god-architect | PRD | .godpowers/arch/ARCH.md |
-| Roadmap | god-roadmapper | PRD, ARCH | .godpowers/roadmap/ROADMAP.md |
-| Stack | god-stack-selector | ARCH | .godpowers/stack/DECISION.md |
+| Design | god-designer | prep, PRD | .godpowers/design/DESIGN.md + .godpowers/design/PRODUCT.md |
+| Architecture | god-architect | PRD, optional DESIGN | .godpowers/arch/ARCH.md |
+| Roadmap | god-roadmapper | PRD, ARCH, optional DESIGN | .godpowers/roadmap/ROADMAP.md |
+| Stack | god-stack-selector | ARCH, optional DESIGN | .godpowers/stack/DECISION.md |
 | Repo | god-repo-scaffolder | DECISION | .godpowers/repo/AUDIT.md + repo files |
 | Deploy | god-deploy-engineer | ARCH, build | .godpowers/deploy/STATE.md |
 | Observe | god-observability-engineer | PRD, ARCH | .godpowers/observe/STATE.md |
@@ -381,7 +424,10 @@ Move to next wave only when ALL slices in current wave are committed.
 After all waves complete:
 1. Run full test suite. All must pass.
 2. Run linter. All clean.
-3. Update PROGRESS.md: Build = done
+3. Run typecheck/check command when the package exposes one. All clean.
+4. If any verification fails, run the autonomous repair loop. Do not mark
+   Build done and do not recommend later work while verification is red.
+5. Update PROGRESS.md: Build = done
 
 CRITICAL RULES (build phase):
 - Never skip god-spec-reviewer
@@ -389,6 +435,8 @@ CRITICAL RULES (build phase):
 - Never commit without BOTH stages passing
 - Each slice gets its own atomic commit
 - Each agent gets a fresh context (defeats context rot)
+- Build cannot be `done` when test, lint, typecheck, or check commands fail
+- A release blocker is a repair target, not the final answer
 
 ## Post-Launch Transition (after Tier 3 completes)
 
@@ -414,8 +462,10 @@ This step runs regardless of flags:
 - /god-mode --conservative -> sync runs (with pause for confirmation)
 - /god-mode --with-hygiene -> sync runs PLUS hygiene check
 
-This ensures every full-arc run leaves the project in a sync'd state. The
-artifact coverage is consistent across all 14 categories.
+After sync, re-run the final verification commands. If any are red, return to
+the autonomous repair loop. This ensures every full-arc run leaves the project
+green and sync'd, not merely documented. The artifact coverage is consistent
+across all 14 categories.
 
 ### Steady-State Hand-off
 
@@ -499,7 +549,8 @@ that should never be auto-accepted. If god-harden-auditor returns Critical
 findings, --yolo does NOT skip. Pause for human resolution.
 
 This is the only --yolo carve-out. All other pauses are auto-resolved with
-the agent's documented default.
+the agent's documented default, and all repairable mechanical failures are
+handled by the autonomous repair loop before the arc can be called complete.
 
 ### Pause Format
 

package/agents/god-planner.md

@@ -1,8 +1,8 @@
 ---
 name: god-planner
 description: |
-  Build planner. Reads roadmap, selects current milestone, breaks into vertical
-  slices, identifies dependencies, groups slices into parallel waves. Each
+  Build planner. Reads roadmap, selects the current delivery increment, breaks
+  it into vertical slices, identifies dependencies, groups slices into waves. Each
   slice plan includes exact file paths, tests-first sequence, and verification
   criteria.
 
@@ -20,10 +20,11 @@ Plan the build.
 
 ## Process
 
-1. Read roadmap, identify current milestone (first non-done)
+1. Read roadmap, identify the current delivery increment (first non-done
+   Now item)
 2. Read ARCH for technical context
 3. Read stack DECISION for tooling
-4. Break milestone into **vertical slices**:
+4. Break the delivery increment into **vertical slices**:
    - Each slice delivers ONE user-visible behavior end-to-end
    - NOT "set up the database" - that's horizontal
    - YES "user can create an account" - includes DB + API + UI for that behavior
@@ -44,7 +45,7 @@ Plan the build.
 Write `.godpowers/build/PLAN.md`:
 
 ```markdown
-# Build Plan: Milestone [N]
+# Build Plan: Delivery Increment [N]
 
 ## Wave 1 (parallel)
 ### Slice 1.1: User can create an account

package/agents/god-roadmapper.md

@@ -1,8 +1,8 @@
 ---
 name: god-roadmapper
 description: |
-  Sequences work into milestones with topological dependency ordering,
-  Now/Next/Later horizons, and observable completion gates. Gated on
+  Sequences work into Godpowers delivery increments with topological dependency
+  ordering, Now/Next/Later horizons, and observable completion gates. Gated on
   Architecture.
 
   Spawned by: /god-roadmap, god-orchestrator
@@ -20,6 +20,8 @@ Optional: `.godpowers/prep/INITIAL-FINDINGS.md` may exist as preparation
 context.
 Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
 context.
+Optional: `.godpowers/design/DESIGN.md` and `.godpowers/design/PRODUCT.md`
+may exist as early product-experience preparation.
 
 ## Imported Preparation Context
 
@@ -27,16 +29,24 @@ If `.godpowers/prep/INITIAL-FINDINGS.md` exists, read it first for repo risks,
 existing tests, docs, CI, deploy, and suggested sequencing implications.
 
 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.
+before sequencing work. Use imported GSD, Superpowers, BMAD, or similar
+stories and plans as hypothesis-level input only. Convert imported terminology
+into Godpowers vocabulary. Do not preserve imported methodology terminology in
+Godpowers artifacts unless the user explicitly asked for it.
+
+If DESIGN.md or PRODUCT.md exists, read them before sequencing delivery
+increments.
+Use screens, flows, components, accessibility obligations, and product voice to
+shape vertical slices and acceptance gates.
 
 Rules:
 - Do not add roadmap features that are not grounded in the PRD.
-- Use imported milestones, stories, and done-work signals to inform ordering,
+- Use imported delivery, story, 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.
+- Keep design-derived delivery increments grounded in the PRD and ARCH.
 
 ## Process
 
@@ -44,10 +54,10 @@ Rules:
 2. List all features from PRD with their priority (MUST/SHOULD/COULD)
 3. Build dependency graph from ARCH (component A depends on component B)
 4. Topologically sort
-5. Group features into milestones:
-   - Each milestone has a clear, substitution-tested goal
-   - Each milestone has an observable completion gate
-   - Each milestone is sized: S/M/L (no day-level precision without capacity input)
+5. Group features into delivery increments:
+   - Each increment has a clear, substitution-tested goal
+   - Each increment has an observable completion gate
+   - Each increment is sized: S/M/L (no day-level precision without capacity input)
 6. Assign Now/Next/Later horizons:
    - **Now**: building right now, committed
    - **Next**: planned next, flexible
@@ -62,7 +72,7 @@ as the structural starting point. Write `.godpowers/roadmap/ROADMAP.md`:
 # Roadmap
 
 ## Now
-### Milestone 1: [substitution-tested name]
+### Delivery Increment 1: [substitution-tested name]
 - Goal: [what users can do when this ships]
 - Gate: [observable completion criteria]
 - Size: S/M/L
@@ -70,20 +80,20 @@ as the structural starting point. Write `.godpowers/roadmap/ROADMAP.md`:
 - Features: [from PRD]
 
 ## Next
-[milestones]
+[delivery increments]
 
 ## Later
-[milestones]
+[themes]
 ```
 
 ## Have-Nots
 
 Roadmap FAILS if:
-- Milestone goal passes substitution test
+- Delivery increment goal passes substitution test
 - Completion gate is not observable
 - Feature appears that is not in the PRD
-- All milestones the same size (no prioritization)
-- No dependency edges between milestones
+- All increments the same size (no prioritization)
+- No dependency edges between increments
 - Day-level precision without capacity input
 - Later section is empty (no long-term vision)
 

package/agents/god-stack-selector.md

@@ -19,6 +19,8 @@ Optional: `.godpowers/prep/INITIAL-FINDINGS.md` may exist as preparation
 context.
 Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
 context.
+Optional: `.godpowers/design/DESIGN.md` and `.godpowers/design/PRODUCT.md`
+may exist as product-experience preparation.
 
 ## Imported Preparation Context
 
@@ -29,11 +31,17 @@ 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.
 
+If DESIGN.md or PRODUCT.md exists, read them before scoring frontend,
+component, styling, accessibility, animation, and design-token tooling
+candidates.
+
 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.
+- If design intent conflicts with ARCH NFRs, ARCH wins and the conflict becomes
+  a stack or architecture open question.
 
 ## Process
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.8",
+  "version": "0.15.10",
   "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,8 @@ execution:
   context: fresh
   reads:
     - .godpowers/prd/PRD.md
+    - .godpowers/design/DESIGN.md
+    - .godpowers/design/PRODUCT.md
     - .godpowers/prep/INITIAL-FINDINGS.md
     - .godpowers/prep/IMPORTED-CONTEXT.md
     - templates/ARCH.md

package/routing/god-design.yaml

@@ -10,14 +10,18 @@ prerequisites:
     - check: file:.godpowers/PROGRESS.md
       reason: "/god-design needs an initialized project"
       auto-complete: /god-init
-    - check: file:.godpowers/stack/DECISION.md
-      reason: "Stack must be selected before design (UI framework drives token shape)"
-      auto-complete: /god-stack
-  optional:
     - check: file:.godpowers/prd/PRD.md
-      reason: "PRD informs target users and register"
+      reason: "Design needs PRD user, product, and register context"
+      auto-complete: /god-prd
+  optional:
+    - check: file:.godpowers/prep/INITIAL-FINDINGS.md
+      reason: "Initial findings can show UI and product-experience signals"
+    - check: file:.godpowers/prep/IMPORTED-CONTEXT.md
+      reason: "Imported GSD, Superpowers, or BMAD context can inform design hypotheses"
     - check: file:.godpowers/arch/ARCH.md
       reason: "ARCH names the UI surface that DESIGN applies to"
+    - check: file:.godpowers/stack/DECISION.md
+      reason: "STACK can refine framework-specific token shape when already selected"
 
 execution:
   spawns: [god-designer]
@@ -47,8 +51,11 @@ standards:
     - "cards in cards"        # impeccable anti-pattern
 
 success-path:
-  next-recommended: /god-repo
-  why: Design tokens stable; repo can scaffold with token references
+  next-recommended: /god-arch
+  why: Early product experience is defined; architecture can now respect the intended surfaces and flows
+  alternatives:
+    - command: /god-repo
+      when: architecture-roadmap-and-stack-already-done
 
 failure-path:
   on-error: /god-doctor

package/routing/god-mode.yaml

@@ -17,7 +17,7 @@ execution:
   reads:
     - .godpowers/prep/INITIAL-FINDINGS.md
     - .godpowers/prep/IMPORTED-CONTEXT.md
-  secondary-spawns: [god-pm, god-architect, god-roadmapper, god-stack-selector, god-repo-scaffolder, god-planner, god-executor, god-spec-reviewer, god-quality-reviewer, god-deploy-engineer, god-observability-engineer, god-harden-auditor, god-launch-strategist]
+  secondary-spawns: [god-pm, god-designer, god-architect, god-roadmapper, god-stack-selector, god-repo-scaffolder, god-planner, god-executor, god-spec-reviewer, god-quality-reviewer, god-deploy-engineer, god-observability-engineer, god-harden-auditor, god-launch-strategist]
   writes:
     []
 

package/routing/god-prd.yaml

@@ -37,6 +37,13 @@ standards:
 
 success-path:
   next-recommended: /god-arch
+  conditional-next:
+    - condition: ui-detected
+      next: /god-design
+      reason: UI or product-experience signals found; write DESIGN.md before architecture
+    - condition: no-ui-detected
+      next: /god-arch
+      reason: No UI surface detected; architecture is the next planning gate
   alternatives:
     - command: /god-mode
       when: user-wants-autonomous-from-here

package/routing/god-roadmap.yaml

@@ -17,6 +17,8 @@ execution:
   reads:
     - .godpowers/prd/PRD.md
     - .godpowers/arch/ARCH.md
+    - .godpowers/design/DESIGN.md
+    - .godpowers/design/PRODUCT.md
     - .godpowers/prep/INITIAL-FINDINGS.md
     - .godpowers/prep/IMPORTED-CONTEXT.md
     - templates/ROADMAP.md

package/routing/god-stack.yaml

@@ -16,6 +16,8 @@ execution:
   context: fresh
   reads:
     - .godpowers/arch/ARCH.md
+    - .godpowers/design/DESIGN.md
+    - .godpowers/design/PRODUCT.md
     - .godpowers/prep/INITIAL-FINDINGS.md
     - .godpowers/prep/IMPORTED-CONTEXT.md
   writes:

package/skills/god-arch.md

@@ -15,8 +15,11 @@ Spawn the **god-architect** agent in a fresh context via Task tool.
 
 1. Verify `.godpowers/prd/PRD.md` exists. If not, tell user to run `/god-prd` first.
 2. Spawn god-auditor briefly to verify PRD passes have-nots. If fails, report and stop.
-3. Spawn god-architect with the PRD path and full context window
-4. The agent writes `.godpowers/arch/ARCH.md` and ADRs to `.godpowers/arch/adr/`
+3. If `.godpowers/design/DESIGN.md` or `.godpowers/design/PRODUCT.md` exists,
+   include it as input. Design is optional, but when present it informs UI
+   containers, routes, flows, and tradeoffs.
+4. Spawn god-architect with the PRD path and full context window
+5. The agent writes `.godpowers/arch/ARCH.md` and ADRs to `.godpowers/arch/adr/`
 
 ## Verification
 

package/skills/god-build.md

@@ -51,13 +51,19 @@ Move to next wave only when current wave is fully committed.
 After all waves:
 1. Run full test suite. All pass.
 2. Run linter. All clean.
-3. Update PROGRESS.md: Build status = done
+3. Run the package's typecheck/check command when present. All pass.
+4. If any verification command fails, do not mark Build complete. Re-enter
+   repair mode with the owning agent, pass the exact failing diagnostics, rerun
+   the command, and repeat until green or until the same root failure survives
+   3 repair attempts.
+5. Update PROGRESS.md: Build status = done
 
 ## Pause Conditions
 
 Pause for user ONLY if:
 - A requirement is genuinely ambiguous (two valid implementations)
 - A test reveals a gap in PRD or ARCH that needs human resolution
+- The same mechanical failure remains after 3 focused repair attempts
 
 ## On Completion
 
@@ -70,8 +76,9 @@ Alternative: /god-deploy (set up deploy pipeline, parallel-safe)
 Both can run; /god-harden is the critical path to Launch.
 ```
 
-If more milestones remain in the roadmap, suggest re-running /god-build for
-the next milestone before moving to Tier 3.
+If more delivery increments remain in the roadmap, continue building the next
+increment before moving to Tier 3 unless the user explicitly asked to stop
+after the current increment.
 
 
 ## Locking

package/skills/god-init.md

@@ -43,6 +43,17 @@ needs to specify a mode.
    - 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.
+   - Detect whether early design preparation is warranted:
+     - UI frameworks or app models: React, Next, Vue, Nuxt, Svelte,
+       SvelteKit, Astro, Remix, Angular, Solid, Flutter, Electron, Tauri
+     - UI surfaces: `src/components/`, `app/`, `pages/`, `routes/`,
+       `public/`, form-heavy flows, dashboards, editor surfaces, mobile
+       shells, marketing pages, or other user-facing product experience
+     - Imported GSD, Superpowers, or BMAD context that mentions UX, screens,
+       journeys, components, brand, interaction states, or visual design
+   - Record the result in `INITIAL-FINDINGS.md` so `/god-prd`, `/god-next`,
+     and `/god-mode` can place `/god-design` after PRD and before
+     `/god-arch` when the project needs early product-experience shape.
 
 3. **Announce findings in plain English** (no jargon):
    - Empty dir + no org context: "Detected: empty directory. Starting fresh."
@@ -121,8 +132,8 @@ needs to specify a mode.
 Always create `.godpowers/prep/INITIAL-FINDINGS.md`. This is Godpowers'
 durable answer to "what did init find in this codebase?" It captures codebase
 shape, framework and tooling signals, tests, CI, docs, AI-tool files, detected
-methodology systems, risk signals, and the reasoning behind the suggested next
-command.
+methodology systems, UI or product-experience signals, risk signals, and the
+reasoning behind the suggested next command.
 
 If GSD, Superpowers, BMAD, or similar planning context is detected, create
 `.godpowers/prep/IMPORTED-CONTEXT.md`. This artifact is preparation context,

package/skills/god-mode.md

@@ -50,6 +50,13 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - Instruction to read `.godpowers/prep/INITIAL-FINDINGS.md` and
      `.godpowers/prep/IMPORTED-CONTEXT.md` if present before choosing the
      first planning or build step
+   - Instruction to run `/god-design` after `/god-prd` and before `/god-arch`
+     when initial findings, imported planning context, the PRD, or the
+     codebase show UI or product-experience signals
+   - Instruction that a red test, typecheck, lint, build, or check command is
+     not a completed arc. It must enter the autonomous repair loop and continue
+     the same `/god-mode` run until green, except for Critical security or a
+     genuine human-only decision.
 
 6. Orchestrator runs the appropriate workflow:
    - Greenfield -> full-arc

package/skills/god-next.md

@@ -45,6 +45,11 @@ next step is safe or why a migration-aware step such as `/god-prd`,
 `/god-map-codebase`, or `/god-mode` is better. Prep artifacts are context only;
 state.json and completed Godpowers artifacts remain authoritative.
 
+If PRD is complete, DESIGN is missing, and initial findings, imported context,
+the PRD, or the codebase show UI or product-experience signals, suggest
+`/god-design` before `/god-arch`. DESIGN.md is early preparation for visible
+workflows, not a replacement for architecture.
+
 ## Process for Mode 1 (post-completion)
 
 ```
@@ -57,7 +62,8 @@ Skill calls: /god-next --after=/god-prd
 Read <runtimeRoot>/routing/god-prd.yaml
    |
    v
-Get success-path.next-recommended (e.g., "/god-arch")
+Get success-path.next-recommended (e.g., "/god-arch"), then apply any
+conditional-next rule such as UI-detected -> "/god-design"
    |
    v
 Display: "PRD complete: .godpowers/prd/PRD.md

package/skills/god-prd.md

@@ -21,6 +21,9 @@ Spawn the **god-pm** agent in a fresh context via Task tool.
 5. The agent writes `.godpowers/prd/PRD.md`
 6. The agent runs have-nots checks before declaring done
 7. If god-pm pauses for a human question: relay to user using pause format
+8. If prep artifacts or the PRD show UI or product-experience signals, route
+   to `/god-design` next so DESIGN.md can shape architecture. Otherwise route
+   to `/god-arch`.
 
 ## Verification
 
@@ -47,7 +50,7 @@ After PRD is written and have-nots pass, print:
 ```
 PRD complete: .godpowers/prd/PRD.md
 
-Suggested next: /god-arch (design the architecture)
+Suggested next: /god-design (shape product experience) if UI/product experience is detected, otherwise /god-arch (design the architecture)
 ```
 
 

package/skills/god-roadmap.md

@@ -1,10 +1,10 @@
 ---
 name: god-roadmap
 description: |
-  Sequence the work into milestones. Spawns the god-roadmapper agent in a
-  fresh context. Gated on Architecture.
+  Sequence the work into Godpowers delivery increments. Spawns the
+  god-roadmapper agent in a fresh context. Gated on Architecture.
 
-  Triggers on: "god roadmap", "/god-roadmap", "sequence the work", "milestone plan"
+  Triggers on: "god roadmap", "/god-roadmap", "sequence the work", "delivery plan"
 ---
 
 # /god-roadmap

package/templates/INITIAL-FINDINGS.md

@@ -19,6 +19,7 @@
 - [HYPOTHESIS] CI or release signals found: [paths or "none detected"].
 - [HYPOTHESIS] Deployment signals found: [paths or "none detected"].
 - [HYPOTHESIS] Documentation signals found: [paths or "none detected"].
+- [HYPOTHESIS] UI or product-experience signals found: [frameworks, routes, components, workflows, design docs, or "none detected"].
 
 ## Methodology And AI Tool Signals
 
@@ -31,6 +32,7 @@
 ## Planning Implications
 
 - [HYPOTHESIS] PRD should pay attention to: [product or user signal].
+- [HYPOTHESIS] Design should pay attention to: [early UX, workflow, brand, component, or interaction signal].
 - [HYPOTHESIS] Architecture should pay attention to: [technical or risk signal].
 - [HYPOTHESIS] Roadmap should pay attention to: [delivery or dependency signal].
 - [HYPOTHESIS] Stack should pay attention to: [tooling or constraint signal].

package/templates/ROADMAP.md

@@ -1,11 +1,11 @@
 # Roadmap
 
-> Every milestone goal is substitution-tested. Every completion gate is
+> Every delivery increment goal is substitution-tested. Every completion gate is
 > observable. No day-level precision without capacity input.
 
 ## Now (currently building, committed)
 
-### Milestone 1: [Substitution-tested goal]
+### Delivery Increment 1: [Substitution-tested goal]
 - **Goal**: [What users can DO when this ships. Specific.]
 - **Completion gate**: [Observable criterion. Not "feels done".]
 - **Size**: S / M / L
@@ -14,20 +14,20 @@
   - [PRD requirement reference]
   - [PRD requirement reference]
 
-### Milestone 2: [Substitution-tested goal]
+### Delivery Increment 2: [Substitution-tested goal]
 - **Goal**: ...
 - **Completion gate**: ...
 - **Size**: S / M / L
-- **Depends on**: Milestone 1
+- **Depends on**: Delivery Increment 1
 - **Features**: ...
 
 ## Next (planned, flexible)
 
-### Milestone 3: [Goal]
+### Delivery Increment 3: [Goal]
 - **Goal**: ...
 - **Completion gate**: ...
 - **Size**: ...
-- **Depends on**: Milestone 2
+- **Depends on**: Delivery Increment 2
 
 ## Later (intent, not commitment)
 
@@ -38,10 +38,10 @@
 
 ## Have-Nots Checklist
 
-- [ ] Every milestone goal fails substitution test
+- [ ] Every delivery increment goal fails substitution test
 - [ ] Every completion gate is observable (not subjective)
 - [ ] No feature appears that isn't in the PRD
-- [ ] Milestones are NOT all the same size (real prioritization)
+- [ ] Delivery increments are NOT all the same size (real prioritization)
 - [ ] Dependency edges are explicit
 - [ ] No day-level precision without capacity input
 - [ ] Later section has at least one theme

package/workflows/full-arc.yaml

@@ -58,6 +58,9 @@ jobs:
         - uses: god-quality-reviewer@^1.0.0
           on-fail: rollback
     on-pass: commit-atomic
+    on-fail: repair-loop
+    verification:
+      required: [test, lint, typecheck-or-check]
 
   deploy:
     tier: 3