godpowers 1.6.12 → 1.6.14

package/routing/god-automation-status.yaml

@@ -0,0 +1,24 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-automation-status
+  description: Show host automation provider support
+  tier: 0
+
+prerequisites:
+  required: []
+
+execution:
+  spawns: [built-in]
+  context: fresh
+  writes: []
+
+success-path:
+  next-recommended: /god-automation-setup
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: tier-0 updated for /god-automation-status
+  events: [agent.start, agent.end]

package/skills/god-automation-setup.md

@@ -0,0 +1,138 @@
+---
+name: god-automation-setup
+description: |
+  Prepare an explicit opt-in setup plan for host-native Godpowers automation.
+  Never creates schedules, routines, background agents, API triggers, or CI
+  workflows without user approval.
+
+  Triggers on: "god automation setup", "set up background automation", "make godpowers proactive"
+---
+
+# /god-automation-setup
+
+Prepare and, after approval, execute safe host-native automation setup.
+
+## Process
+
+1. Resolve the runtime root and load `<runtimeRoot>/lib/automation-providers.js`.
+2. Call `automation.setupPlan(projectRoot)`.
+3. Print `automation.renderSetupPlan(plan)`.
+4. Ask the user to choose:
+   - provider
+   - templates
+   - cadence
+   - connector or repository scope
+   - whether write actions are allowed
+5. If the plan reports `execution.directHostToolCalling: true`, and the user
+   approved the exact provider, template, cadence, and scope, use the host
+   automation tool or native command from `execution`.
+6. If setup is complex, write-capable, multi-template, background-agent based,
+   scriptable-scheduler based, or provider-uncertain, spawn
+   `god-automation-engineer` with the approved provider, templates, cadence,
+   scope, and plan output.
+7. If no host tool is callable, return exact manual setup steps and do not
+   record an active automation.
+8. After host setup succeeds, write or update `.godpowers/automations.json`
+   through `automation.buildAutomationRecord(...)` and
+   `automation.recordAutomation(..., { confirmedHostSuccess: true })` with:
+   - automation id
+   - provider id
+   - status
+   - cadence
+   - prompt summary
+   - created timestamp
+   - host surface used
+9. Run `/god-automation-status` after setup and show the result.
+
+## Tool Calling And Agent Use
+
+Use host tool calling when available for simple, approved, read-only setup:
+
+- Codex App: call the Codex automation tool.
+- Claude Code: use the schedule or routine surface.
+- Cline: use `cline schedule`.
+- Qwen Code: use `/loop` and report that it is session-scoped.
+
+Spawn `god-automation-engineer` when any of these are true:
+
+- more than one template is requested
+- any write-capable automation is requested
+- provider setup needs background agents, API triggers, CI, OS scheduling, or
+  repository scope
+- the host tool exists but the setup requires multiple steps
+- provider capability is uncertain
+
+## Hard Stops
+
+Do not create automations during install.
+
+Do not create any automation that can do these unless the user explicitly asks
+for that exact write-capable automation:
+
+- stage, commit, push, merge, package, publish, or release
+- deploy to staging or production
+- access provider dashboards, DNS, credentials, secrets, or billing
+- clear `.godpowers/REVIEW-REQUIRED.md`
+- accept Critical security findings
+- run broad dependency upgrades
+- delete files, reset branches, or clean worktrees
+
+## Safe Starting Templates
+
+- `daily-status`: run `godpowers status --project .` and summarize current phase, progress, open items, and next action
+- `stale-checkpoint`: inspect checkpoint freshness and suggest `/god-sync` or `/god-resume-work`
+- `review-queue`: report unresolved review items without clearing them
+- `weekly-hygiene`: report docs, dependencies, checkpoint, reviews, and hygiene signals
+- `release-readiness`: report release readiness without publishing
+
+## Provider Guidance
+
+- Codex App: use native Codex automations when the host exposes them.
+- Claude Code: use `/schedule` for scheduled routines. Use Claude web for API or GitHub triggers.
+- Cline: use `cline schedule` or the Cline SDK scheduler.
+- Kilo: use KiloClaw Scheduled Triggers.
+- Qwen Code: use `/loop` only for session-scoped checks and report that it is not durable.
+- Cursor: use Background Agents or the Background Agent API for branch-scoped async work.
+- GitHub Copilot: use issues, pull requests, or Copilot cloud agent entry points.
+- Windsurf: install workflows or skills, but report that workflows are manual-only.
+- Gemini CLI, OpenCode, CodeBuddy, and Pi: use headless or SDK execution only with an approved scheduler.
+- Trae and Antigravity: report scheduled automation as unknown unless the host proves otherwise.
+
+## Output Shape
+
+```text
+Godpowers Automation Setup Plan
+
+Recommended provider: <provider>
+
+Setup steps:
+  1. <host-native setup step>
+
+Execution path:
+  - Method: <host-tool-calling | host-native-command | local-command | manual>
+  - Action: <approved host action>
+  - Direct host tool calling: <available after approval | not available>
+  - Specialist agent: <god-automation-engineer | not required>
+  - Record after success: .godpowers/automations.json
+
+Recommended safe templates:
+  - <template id>: <prompt>
+
+Approval required:
+  - Choose a provider
+  - Choose one or more templates
+  - Confirm any host-native schedule, routine, background agent, API trigger, or connector scope
+```
+
+## Proposition Closeout
+
+End with:
+
+```text
+Proposition:
+  1. Implement partial: create one read-only automation after approval
+  2. Implement complete: create all safe read-only automations after approval
+  3. Discuss more: tune provider, cadence, or safety rules
+  4. Inspect status: /god-automation-status
+Recommended: <one option tied to provider capability and user risk>
+```

package/skills/god-automation-status.md

@@ -0,0 +1,76 @@
+---
+name: god-automation-status
+description: |
+  Show host-native automation provider support for the current project.
+  Reports Codex App, Claude Routines, Cline schedules, Qwen loops, Cursor
+  background agents, Copilot cloud agent, and scriptable CLI providers.
+
+  Triggers on: "god automation status", "automation support", "background automation status"
+---
+
+# /god-automation-status
+
+Show which automation providers Godpowers can safely use in this project.
+
+## Process
+
+1. Resolve the runtime root and load `<runtimeRoot>/lib/automation-providers.js`.
+2. Call `automation.detect(projectRoot)`.
+3. Print `automation.render(result)`.
+4. Read `.godpowers/automations.json` if present and report active automations.
+5. Do not create, update, trigger, pause, resume, or delete schedules.
+6. Do not stage, commit, push, publish, deploy, clear review queues, or access
+   provider dashboards.
+
+If the executable runtime module is unavailable, manually report these provider
+classes:
+
+- native-scheduler: Codex App automations, Claude Code routines, Cline schedules, Kilo scheduled triggers
+- session-scheduler: Qwen Code `/loop`
+- background-agent: Cursor Background Agents, GitHub Copilot cloud agent
+- scriptable-headless: Gemini CLI, OpenCode, CodeBuddy SDK, Pi SDK
+- manual-workflow: Windsurf workflows, Augment subagents
+- unknown: Trae, Antigravity scheduled automation
+
+## Output Shape
+
+```text
+Godpowers Automation Providers
+
+Config: .godpowers/automations.json
+Recommended provider: <provider or none available>
+
+Active automations:
+  - <id via provider: status or none recorded>
+
+Provider status:
+  - <provider>: <status> (<class>)
+
+Safe templates:
+  - daily-status: Daily Godpowers status, Daily at 9am local time, read-only
+  - stale-checkpoint: Stale checkpoint watcher, Weekdays at 9am local time, read-only
+  - review-queue: Review queue watcher, Daily at 10am local time, read-only
+  - weekly-hygiene: Weekly hygiene report, Monday at 9am local time, read-only
+  - release-readiness: Release readiness report, Manual or before release, read-only
+
+Safety rules:
+  - Do not create automations during install.
+  - Create schedules, routines, background agents, or API triggers only after explicit user approval.
+  - Default templates are read-only.
+```
+
+## Proposition Closeout
+
+End with:
+
+```text
+Proposition:
+  1. Implement partial: /god-automation-setup for one safe read-only template
+  2. Implement complete: /god-automation-setup for all safe templates supported by the current host
+  3. Discuss more: /god-discuss automation policy and provider choice
+  4. Inspect status: /god-status to see project progress and automation status together
+Recommended: <one option tied to the detected provider>
+```
+
+If no provider is available, recommend manual `/god-next` or
+`godpowers next --project .`.

package/skills/god-doctor.md

@@ -46,8 +46,8 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 106 skills installed
-  [OK] 39 agents installed
+  [OK] 108 skills installed
+  [OK] 40 agents installed
   [OK] VERSION matches (1.6.6)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 

package/skills/god-status.md

@@ -97,6 +97,7 @@ Proactive opportunities:
   Sync: fresh
   Docs: possible drift, suggest /god-docs
   Runtime: known local URL, suggest /god-test-runtime
+  Automation: available via codex-app, suggest /god-automation-setup
   Security: clear
   Dependencies: clear
   Hygiene: stale, suggest /god-hygiene
@@ -174,6 +175,8 @@ Report:
   `docs drift-check already logged`
 - Runtime: `not-applicable`, `known URL, suggest /god-test-runtime`, or
   `no known URL, defer deployed verification`
+- Automation: `not configured`, `<N> active`, or
+  `available via <provider>, suggest /god-automation-setup`
 - Security: `clear` or `sensitive files changed, suggest /god-harden`
 - Dependencies: `clear` or `dependency files changed, suggest /god-update-deps`
 - Hygiene: `fresh` or `stale, suggest /god-hygiene`

package/skills/god-version.md

@@ -16,7 +16,7 @@ Print version and a short capability summary.
 ```
 Godpowers v1.6.6
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 106 skills, 39 agents, 13 workflows, 36 recipes
+Surface: 108 skills, 40 agents, 13 workflows, 36 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 ```