@liangjie559567/ultrapower 5.1.0 → 5.2.0

package/skills/nexus/nexus-status/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: nexus-status
+description: 查看 nexus 系统状态
+triggers:
+  - nexus status
+  - nexus-status
+  - nexus health
+---
+
+# nexus Status
+
+显示 nexus 系统当前状态。
+
+## 执行步骤
+
+1. 读取 `.omc/nexus/config.json`，检查 `enabled` 字段（若字段缺失则默认为 false）确认 nexus 是否启用
+2. 检查 `.omc/nexus/events/` 目录，统计待推送事件数量。如果该目录不存在，将计数视为 0。
+3. 检查 `.omc/nexus/improvements/` 目录，统计待审批改进数量。如果该目录不存在，将计数视为 0。
+4. 读取 `.omc/nexus/config.json` 中的 `last_sync` 字段作为最后同步时间；若该字段不存在则显示 'never'。
+5. 输出状态摘要：
+
+```
+nexus Status
+============
+Enabled: true/false
+Pending events: N
+Pending improvements: N
+Last sync: <timestamp or "never">
+```
+
+如果 nexus 未启用，提示用户配置 `.omc/nexus/config.json`。

package/skills/release/SKILL.md

@@ -27,10 +27,12 @@ description: ultrapower 的自动化发布工作流
 - `.claude-plugin/plugin.json`
 - `.claude-plugin/marketplace.json`（`"version"` 和 `"source.version"` 两处）
 - `docs/CLAUDE.md`（`<!-- OMC:VERSION:X.Y.Z -->`）
+- `CLAUDE.md`（`ultrapower vX.Y.Z 规范体系位于 \`docs/standards/\``）
 - `README.md`（版本徽章和标题）
 
 > ⚠️ `marketplace.json` 是安装器读取的入口，版本不同步会导致用户始终安装旧版本。
 > ⚠️ `docs/CLAUDE.md` 是 `/ultrapower:omc-setup` 下载的模板，版本不同步会导致用户安装后显示旧版本号。
+> ⚠️ `CLAUDE.md` 是开发规范文档，版本引用不同步会导致开发者参考错误的规范版本。
 
 ### 2. 运行测试
 ```bash
@@ -82,6 +84,7 @@ gh release create v<version> --title "v<version> - <title>" --notes "<release no
 | `.claude-plugin/plugin.json` | `"version": "X.Y.Z"` |
 | `.claude-plugin/marketplace.json` | `"version": "X.Y.Z"` 和 `"source": { "version": "X.Y.Z" }` |
 | `docs/CLAUDE.md` | `<!-- OMC:VERSION:X.Y.Z -->` |
+| `CLAUDE.md` | `ultrapower vX.Y.Z 规范体系位于 \`docs/standards/\`` |
 | `README.md` | 标题 + 版本徽章 |
 
 ## 语义化版本

package/skills/requesting-code-review/SKILL.md

@@ -58,7 +58,7 @@ HEAD_SHA=$(git rev-parse HEAD)
 
 [Dispatch superpowers:code-reviewer subagent]
   WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
-  PLAN_OR_REQUIREMENTS: Task 2 from docs/plans/deployment-plan.md
+  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
   BASE_SHA: a7981ec
   HEAD_SHA: 3df7661
   DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types

package/skills/using-superpowers/references/codex-tools.md

@@ -0,0 +1,25 @@
+# Codex Tool Mapping
+
+Skills use Claude Code tool names. When you encounter these in a skill, use your platform equivalent:
+
+| Skill references | Codex equivalent |
+|-----------------|------------------|
+| `Task` tool (dispatch subagent) | `spawn_agent` |
+| Multiple `Task` calls (parallel) | Multiple `spawn_agent` calls |
+| Task returns result | `wait` |
+| Task completes automatically | `close_agent` to free slot |
+| `TodoWrite` (task tracking) | `update_plan` |
+| `Skill` tool (invoke a skill) | Skills load natively — just follow the instructions |
+| `Read`, `Write`, `Edit` (files) | Use your native file tools |
+| `Bash` (run commands) | Use your native shell tools |
+
+## Subagent dispatch requires collab
+
+Add to your Codex config (`~/.codex/config.toml`):
+
+```toml
+[features]
+collab = true
+```
+
+This enables `spawn_agent`, `wait`, and `close_agent` for skills like `dispatching-parallel-agents` and `subagent-driven-development`.

package/skills/writing-plans/plan-document-reviewer-prompt.md

@@ -0,0 +1,52 @@
+# Plan Document Reviewer Prompt Template
+
+Use this template when dispatching a plan document reviewer subagent.
+
+**Purpose:** Verify the plan chunk is complete, matches the spec, and has proper task decomposition.
+
+**Dispatch after:** Each plan chunk is written
+
+```
+Task tool (general-purpose):
+  description: "Review plan chunk N"
+  prompt: |
+    You are a plan document reviewer. Verify this plan chunk is complete and ready for implementation.
+
+    **Plan chunk to review:** [PLAN_FILE_PATH] - Chunk N only
+    **Spec for reference:** [SPEC_FILE_PATH]
+
+    ## What to Check
+
+    | Category | What to Look For |
+    |----------|------------------|
+    | Completeness | TODOs, placeholders, incomplete tasks, missing steps |
+    | Spec Alignment | Chunk covers relevant spec requirements, no scope creep |
+    | Task Decomposition | Tasks atomic, clear boundaries, steps actionable |
+    | File Structure | Files have clear single responsibilities, split by responsibility not layer |
+    | File Size | Would any new or modified file likely grow large enough to be hard to reason about as a whole? |
+    | Task Syntax | Checkbox syntax (`- [ ]`) on steps for tracking |
+    | Chunk Size | Each chunk under 1000 lines |
+
+    ## CRITICAL
+
+    Look especially hard for:
+    - Any TODO markers or placeholder text
+    - Steps that say "similar to X" without actual content
+    - Incomplete task definitions
+    - Missing verification steps or expected outputs
+    - Files planned to hold multiple responsibilities or likely to grow unwieldy
+
+    ## Output Format
+
+    ## Plan Review - Chunk N
+
+    **Status:** Approved | Issues Found
+
+    **Issues (if any):**
+    - [Task X, Step Y]: [specific issue] - [why it matters]
+
+    **Recommendations (advisory):**
+    - [suggestions that don't block approval]
+```
+
+**Reviewer returns:** Status, Issues (if any), Recommendations