godpowers 0.15.17 → 1.0.0

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "godpowers",
-  "version": "0.15.17",
+  "version": "1.0.0",
   "description": "AI-powered development system: 105 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.",
   "bin": {
     "godpowers": "./bin/install.js"
   },
   "scripts": {
-    "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-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",
+    "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",
     "prepublishOnly": "npm test",
     "validate-skills": "node scripts/validate-skills.js",
     "test:surface": "node scripts/test-doc-surface-counts.js",
@@ -15,6 +15,7 @@
     "test:router": "node scripts/test-router.js",
     "test:recipes": "node scripts/test-recipes.js",
     "test:context": "node scripts/test-context-writer.js",
+    "test:pillars": "node scripts/test-pillars.js",
     "test:linter": "node scripts/test-artifact-linter.js",
     "test:diff": "node scripts/test-artifact-diff.js"
   },
@@ -71,6 +72,7 @@
     "lib/",
     "extensions/",
     "INSPIRATION.md",
+    "RELEASE.md",
     "SKILL.md",
     "AGENTS.md",
     "CHANGELOG.md",

package/skills/god-build.md

@@ -19,6 +19,10 @@ Orchestrate the build via specialist agents.
    - `.godpowers/stack/DECISION.md` exists (skip if scale is trivial)
    - Repo is scaffolded
 2. If any gate fails: tell user which command to run first
+3. Compute the Pillars load set for the build task with
+   `lib/pillars.computeLoadSet(projectRoot, taskText)`. Always load
+   `agents/context.md` and `agents/repo.md`, then pass only task-relevant
+   pillars into each planner or executor context.
 
 ## Orchestration
 
@@ -57,6 +61,9 @@ After all waves:
    the command, and repeat until green or until the same root failure survives
    3 repair attempts.
 5. Update PROGRESS.md: Build status = done
+6. If the build plan or implementation establishes durable conventions, plan
+   pillar updates through `lib/pillars.planArtifactSync`. Under
+   `/god-mode --yolo`, apply those updates immediately and log the decision.
 
 ## Pause Conditions
 

package/skills/god-context.md

@@ -1,9 +1,10 @@
 ---
 name: god-context
 description: |
-  Manage the Godpowers fenced section in project-level AI instruction files
-  (AGENTS.md, CLAUDE.md, GEMINI.md, .cursor/rules/, .windsurfrules,
-  .github/copilot-instructions.md, .clinerules, .roo/, .continue/).
+  Manage native Pillars project context plus the Godpowers fenced section in
+  project-level AI instruction files (AGENTS.md, CLAUDE.md, GEMINI.md,
+  .cursor/rules/, .windsurfrules, .github/copilot-instructions.md,
+  .clinerules, .roo/, .continue/).
 
   Triggers on: "god context", "/god-context", "tell ai tools", "ai instructions",
   "context off", "context status", "agents.md", "claude.md", "gemini.md"
@@ -11,33 +12,46 @@ description: |
 
 # /god-context
 
-Tell your AI coding tools that this is a Godpowers project. The skill writes
-a fenced section to `AGENTS.md` (canonical) and 1-line pointer fences to any
+Tell your AI coding tools that this is a Godpowers project. Godpowers projects
+use Pillars as the native project context layer: root `AGENTS.md` plus
+`agents/*.md` pillar files. This skill keeps that layer present and writes a
+Godpowers fenced section to `AGENTS.md` plus 1-line pointer fences to any
 detected tool's instruction file (CLAUDE.md, GEMINI.md, etc.). You can turn
-it off, check status, or refresh on demand.
+the Godpowers fences off, check status, or refresh on demand.
 
 ## Subcommands
 
 | Form | What it does |
 |---|---|
 | `/god-context` (no args) | Same as `status`. |
-| `/god-context on` | Write AGENTS.md and pointers for any detected AI tools. |
-| `/god-context off` | Remove the Godpowers fence from every target file. |
-| `/god-context status` | Show which targets have a fence and which tools were detected. |
+| `/god-context on` | Ensure Pillars exists, then write AGENTS.md and pointers for any detected AI tools. |
+| `/god-context off` | Remove the Godpowers fence from every target file. Leave Pillars intact. |
+| `/god-context status` | Show Pillars health, which targets have a fence, and which tools were detected. |
 | `/god-context refresh` | Same as `on`. Re-derives content from current state. |
 
 ## Process
 
 1. Verify `.godpowers/` exists. If not, suggest `/god-init` first.
 2. Read `.godpowers/state.json`.
-3. Spawn `god-context-writer` agent with the requested mode.
-4. Report results.
+3. Call `lib/pillars.detect(projectRoot)`.
+4. If Pillars is absent or partial, call `lib/pillars.init(projectRoot)`.
+5. Spawn `god-context-writer` agent with the requested mode.
+6. Report results.
 
 ## What gets written
 
-**Always (canonical):**
+**Always (native project context):**
 
-- `AGENTS.md` - full Godpowers section (under 30 lines)
+- `AGENTS.md` - Pillars loading protocol plus the Godpowers fenced section
+- `agents/context.md` - always-loaded project identity and product invariants
+- `agents/repo.md` - always-loaded repository layout and naming conventions
+- Core pillar stubs for `stack`, `arch`, `data`, `api`, `ui`, `auth`,
+  `quality`, `deploy`, and `observe`
+
+**Godpowers managed fence:**
+
+- `AGENTS.md` - full Godpowers section (under 30 lines), inside the
+  `godpowers` fence
 
 **Only if detected (pointer):**
 
@@ -122,8 +136,8 @@ When `/god-sync` runs (post-arc, or any sync), `god-updater` calls this skill
 with `refresh` to keep `AGENTS.md` content aligned with the latest project
 state (mode, scale, completed tiers, active artifacts).
 
-You can disable this by running `/god-context off`. It won't be re-enabled
-without your explicit `/god-context on`.
+You can disable the Godpowers fences by running `/god-context off`. Pillars
+remains because it is the native context contract for Godpowers projects.
 
 ## Privacy / portability
 

package/skills/god-doctor.md

@@ -48,7 +48,7 @@ GODPOWERS DOCTOR
 Install: claude (~/.claude/)
   [OK] 105 skills installed
   [OK] 39 agents installed
-  [OK] VERSION matches (0.15.17)
+  [OK] VERSION matches (1.0.0)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/

package/skills/god-extension-info.md

@@ -31,7 +31,7 @@ Description:
   specific checks.
 
 Engines:
-  godpowers: >=0.14.0 <2.0.0  (compatible with running v0.15.17? YES)
+  godpowers: >=0.14.0 <2.0.0  (compatible with running v1.0.0? YES)
 
 Provides:
   Agents (3):

package/skills/god-feature.md

@@ -30,6 +30,10 @@ Add a feature to an already-existing project.
 
 1. Verify `.godpowers/` exists. If not, fall back to /god-init first.
 2. Read existing PRD, ARCH, ROADMAP for context
+3. Compute the Pillars load set for the feature request with
+   `lib/pillars.computeLoadSet(projectRoot, taskText)`. Load
+   `agents/context.md` and `agents/repo.md` first, then task-routed pillars
+   such as `auth`, `data`, `api`, `ui`, or `quality`.
 
 ## Orchestration
 
@@ -65,6 +69,11 @@ audited at .godpowers/harden/FINDINGS.md."
 No landing page. No marketing. The feature ships behind a flag, gradually
 enabled. Update CHANGELOG.
 
+### Phase 7: Pillars sync
+If the feature changes durable project truth, plan updates through
+`lib/pillars.planArtifactSync`. Default mode proposes the pillar edits for
+review. Under `/god-mode --yolo`, apply them immediately and log the decision.
+
 ## On Completion
 
 ```

package/skills/god-init.md

@@ -2,8 +2,8 @@
 name: god-init
 description: |
   Initialize a Godpowers project. Detects operating mode (greenfield, gap-fill,
-  audit, multi-repo) and project scale. Creates .godpowers/ directory with
-  PROGRESS.md.
+  audit, multi-repo) and project scale. Creates native Pillars project context
+  plus the .godpowers/ workflow state directory with PROGRESS.md.
 
   Triggers on: "god init", "start a project", "new project", "initialize"
 ---
@@ -18,8 +18,9 @@ This skill is a thin wrapper. Detection happens automatically; user never
 needs to specify a mode.
 
 1. Check if `.godpowers/` already exists:
-   - If yes: read PROGRESS.md, report current state, ask if user wants to
-     reset or resume
+   - If yes: read PROGRESS.md, call `lib/pillars.pillarizeExisting(projectRoot)`
+     to ensure the existing Godpowers project is also Pillar-ized, report
+     current state, ask if user wants to reset or resume
    - If no: proceed with initialization
 
 2. **Auto-detect what kind of project this is** (background, no user prompt):
@@ -55,7 +56,23 @@ needs to specify a mode.
      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):
+3. **Initialize native Pillars context**:
+   - Call `lib/pillars.init(projectRoot, findings)`.
+   - Ensure root `AGENTS.md` contains the Pillars loading protocol.
+   - Ensure `agents/context.md` and `agents/repo.md` exist with
+     `always_load: true`.
+   - Ensure Tier 1 Core pillar stubs exist for `stack`, `arch`, `data`, `api`,
+     `ui`, `auth`, `quality`, `deploy`, and `observe`.
+   - Preserve existing files. Create missing pillars as `status: stub` unless
+     Godpowers has strong evidence to mark them `present`.
+   - For an existing `.godpowers/` project, call
+     `lib/pillars.pillarizeExisting(projectRoot)` so current PRD, ARCH, STACK,
+     ROADMAP, BUILD, DEPLOY, OBSERVE, HARDEN, DESIGN, and PRODUCT artifacts
+     become managed source references in the relevant pillars.
+   - This is not optional for Godpowers projects. A Godpowers project is a
+     Pillars project by default.
+
+4. **Announce findings in plain English** (no jargon):
    - Empty dir + no org context: "Detected: empty directory. Starting fresh."
    - Empty dir + org context: "Detected: empty directory + org standards.
      I'll respect your org's tooling/infrastructure choices."
@@ -75,6 +92,8 @@ needs to specify a mode.
    - Write `.godpowers/prep/INITIAL-FINDINGS.md`
    - Run planning-system context detection for GSD, Superpowers, and BMAD
    - Write `.godpowers/prep/IMPORTED-CONTEXT.md` when useful context exists
+   - Initialize native Pillars context and record Pillars health in
+     `INITIAL-FINDINGS.md`
    - For brownfield: schedule archaeology + reconstruction as preflight
    - For bluefield: load org-context as constraint
    - Create directory structure
@@ -90,6 +109,19 @@ needs to specify a mode.
 
 5. Create the directory structure:
    ```
+   AGENTS.md
+   agents/
+     context.md
+     repo.md
+     stack.md
+     arch.md
+     data.md
+     api.md
+     ui.md
+     auth.md
+     quality.md
+     deploy.md
+     observe.md
    .godpowers/
      PROGRESS.md
      prep/
@@ -132,17 +164,22 @@ 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, UI or product-experience signals, risk signals, and the
-reasoning behind the suggested next command.
+methodology systems, Pillars health, 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,
 not source of truth. It feeds PRD, architecture, roadmap, and stack decisions
 as hypothesis-level input only.
 
-## AI-tool context (automatic for explicit init)
+## Native Pillars context and AI-tool context
 
-After PROGRESS.md is written, decide from the trigger phrase:
+After PROGRESS.md is written, Pillars context is already present. Every
+Godpowers project uses `AGENTS.md` plus `agents/*.md` as its native project
+truth layer.
+
+Then decide from the trigger phrase whether to write Godpowers pointer fences
+for individual AI tools:
 
 - If the user explicitly invoked `god init` or `/god-init`, write AI-tool
   context automatically. The command itself is explicit consent to initialize

package/skills/god-mode.md

@@ -19,7 +19,9 @@ You are receiving a /god-mode invocation. Your job is to spawn the
 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.
+     to describe the project again. Call
+     `lib/pillars.pillarizeExisting(projectRoot)` first, then 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."
@@ -34,6 +36,8 @@ You are receiving a /god-mode invocation. Your job is to spawn the
      "How to announce" section)
 
 3. Load durable resume context before asking anything:
+   - Pillars load set from `lib/pillars.computeLoadSet(projectRoot, taskText)`,
+     starting with `agents/context.md` and `agents/repo.md`
    - `.godpowers/CHECKPOINT.md` first, when present
    - `.godpowers/state.json`
    - `.godpowers/PROGRESS.md`
@@ -74,6 +78,8 @@ 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 compute and load the Pillars load set before every major
+     command, because Pillars is the native project context layer
    - 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
@@ -162,7 +168,9 @@ Default: If you say "go", I'll pick [X] because [Y].
 
 ### --yolo
 Pass through to orchestrator. Orchestrator picks defaults at every pause point
-and logs decisions to `.godpowers/YOLO-DECISIONS.md`.
+and logs decisions to `.godpowers/YOLO-DECISIONS.md`. Pillar sync proposals
+generated from durable Godpowers artifact changes are auto-applied in this
+mode and logged as YOLO decisions.
 
 ### --conservative
 Pass through. Orchestrator pauses at every tier boundary.
@@ -198,6 +206,16 @@ Under `--yolo`, the sync step auto-applies (no pause). Under
 `--conservative`, it pauses for confirmation. Under `--with-hygiene`,
 it runs alongside the hygiene pass.
 
+The sync step also reconciles native Pillars context. When `.godpowers`
+artifacts create or change durable project truth, Godpowers maps those changes
+to relevant pillar files through `lib/pillars.planArtifactSync`. Default mode
+proposes pillar updates for review. `--yolo` applies them immediately and logs
+the action to `.godpowers/YOLO-DECISIONS.md`.
+
+If `/god-mode` resumes an existing `.godpowers` project that lacks Pillars,
+it Pillar-izes the project before continuing. Existing `.godpowers` artifacts
+become managed source references in the relevant `agents/*.md` files.
+
 The sync step is what closes the loop between greenfield arc creation and
 the comprehensive 14-artifact reconciliation system. See
 `docs/greenfield-coverage.md` for what's created when.

package/skills/god-review.md

@@ -15,7 +15,11 @@ Spawn two specialist review agents in fresh contexts via Task tool.
 
 1. Gather context: what code is being reviewed? (recent diff, specific files, PR)
 2. Locate the relevant plan or PRD acceptance criteria
-3. Run Stage 1 first, then Stage 2 only if Stage 1 passes
+3. Compute the Pillars load set from the task and changed files with
+   `lib/pillars.computeLoadSet(projectRoot, taskText)`. Reviews may cite
+   violations of `agents/auth.md`, `agents/data.md`, `agents/ui.md`, or any
+   other loaded pillar directly.
+4. Run Stage 1 first, then Stage 2 only if Stage 1 passes
 
 ## Stage 1: Spec Compliance
 

package/skills/god-sync.md

@@ -29,7 +29,10 @@ User runs `/god-sync` after manual changes. Useful for:
 ## Setup
 
 1. Verify `.godpowers/` exists
-2. Spawn god-updater in fresh context with:
+2. Call `lib/pillars.pillarizeExisting(projectRoot)` if Pillars is absent or
+   partial, because every Godpowers project must also carry native Pillars
+   context.
+3. Spawn god-updater in fresh context with:
    - The reconciliation verdict (if available from a prior /god-reconcile)
    - Or: re-run reconciliation against current state to detect what changed
    - Recent commits for context
@@ -39,8 +42,10 @@ User runs `/god-sync` after manual changes. Useful for:
 After god-updater returns:
 1. Verify each touched artifact passes its tier's have-nots
 2. Verify SYNC-LOG.md was appended
-3. Verify state.json reflects new tier statuses
-4. Display summary of what changed
+3. Verify Pillars source sections were updated for any changed durable
+   artifact. Under `--yolo`, pillar updates are auto-applied and logged.
+4. Verify state.json reflects new tier statuses
+5. Display summary of what changed
 
 ## Output
 
@@ -74,6 +79,7 @@ Suggested next: /god-status
 | Backlog cruft | Resolved entries linked to commits |
 | Orphan todos | Closes superseded todos |
 | Lost threads | Active threads get progress notes |
+| Pillars drift | Keeps `agents/*.md` aligned with current `.godpowers` artifacts |
 
 The loop:
 

package/skills/god-version.md

@@ -14,7 +14,7 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v0.15.17
+Godpowers v1.0.0
 Install: /Users/.../.claude/  (matches package.json)
 Surface: 105 skills, 39 agents, 13 workflows, 36 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1

package/templates/IMPORTED-CONTEXT.md

@@ -36,5 +36,6 @@
 
 - [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] This artifact must not override native Pillars files under `agents/*.md`.
 - [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.

package/templates/INITIAL-FINDINGS.md

@@ -27,6 +27,7 @@
 - [HYPOTHESIS] GSD context found: [paths or "none detected"].
 - [HYPOTHESIS] Superpowers context found: [paths or "none detected"].
 - [HYPOTHESIS] BMAD context found: [paths or "none detected"].
+- [HYPOTHESIS] Pillars context health: [present / partial / initialized].
 - [HYPOTHESIS] Imported context artifact: [.godpowers/prep/IMPORTED-CONTEXT.md or "not created"].
 
 ## Planning Implications
@@ -51,4 +52,5 @@
 
 - [DECISION] Downstream agents may use this artifact as preparation context only.
 - [DECISION] If this artifact conflicts with `.godpowers/intent.yaml`, `.godpowers/state.json`, `PROGRESS.md`, or a completed Godpowers artifact, the Godpowers artifact wins.
+- [DECISION] Pillars files under `agents/*.md` are the native project context layer for Godpowers commands.
 - [DECISION] Imported GSD, Superpowers, and BMAD signals must be converted into Godpowers-native artifacts, not preserved as parallel state.