ultra-builder-pro-cli 0.10.0 → 0.11.0

package/commands/ultra-deliver.md

@@ -1,52 +1,10 @@
 ---
-description: Converge and deliver a verified baseline or continuous change — reconcile specs, archive evidence, version, tag, and push
+description: Converge current evidence and specification learning into an archived or released baseline
 argument-hint: "[version-type]"
-allowed-tools: Task, Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion
-model: opus
 workflow-ref: "@skills/ultra-deliver/SKILL.md"
-cli_fallback: "direct user interaction"
-mcp_tools_required:
-  - change.list
-  - change.get
-  - change.context
-  - change.converge
-  - change.archive
 ---
 
-# /ultra-deliver
+# Converge and deliver
 
-## 目标
-
-`/ultra-test` 绿灯后，把 active delta 合并回 baseline，重跑发布证据，调用
-`change.converge` 与 `change.archive`，再完成版本号、tag、push 和 delivery report。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | 版本跳跃（`patch`/`minor`/`major`） | 按 commit 类型自动判断 |
-
-## Workflow
-
-完整流程见 `@skills/ultra-deliver/SKILL.md`（绑定 change → baseline reconciliation →
-build/test → release commit → context/convergence/archive → tag/push → report）。
-
-**命令入口做的事**：
-1. 读 `.ultra/test-report.json` 验 `passed=true` + `git_commit === HEAD`
-2. `git status` 清洁检查；不干净 → 通过 Host 原生提问界面选处理方式
-3. 有 active change 时合并 delta、刷新 context，并通过确定性 convergence gate
-4. archive 完成后才允许 tag/push
-5. 写带 change id、archive path、baseline updates 的 delivery report
-
-## 用法
-
-```bash
-/ultra-deliver              # 自动判断版本号
-/ultra-deliver major        # 强制 major bump（breaking changes）
-/ultra-deliver patch        # 强制 patch
-```
-
-## 下一步
-
-部署到 Railway / Vercel，或在 release channel 广播。`delivery-report.json` 里
-`pushed=true` 后即可视作发布完成。
+Read and follow `@skills/ultra-deliver/SKILL.md`, using `$ARGUMENTS` only for an explicitly requested version policy.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-dev.md

@@ -1,54 +1,10 @@
 ---
-description: Agile development execution — one task through TDD + review gate, writing state via MCP task.update
+description: Execute one authoritative Ultra task through implementation, verification, and review
 argument-hint: "[task-id]"
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, AskUserQuestion, Skill
-model: opus
 workflow-ref: "@skills/ultra-dev/SKILL.md"
-mcp_tools_required:
-  - task.update
-  - task.get
-  - task.list
-  - change.get
-  - change.context
 ---
 
-# /ultra-dev
+# Execute one Ultra task
 
-## 目标
-
-把一个 task 从 `pending` 推到 `completed`：进入 feature 分支 → RED/GREEN/REFACTOR
-TDD → 质量门 → `/ultra-review all` → 完成 → commit/merge。**单写**：状态只通过
-MCP `task.update` 改一次；projector 自动更新 tasks.json + context-md frontmatter。
-MCP 状态工具失败时 fail closed；`LEGACY_STATE_MIGRATION_REQUIRED` 只允许先跑
-v4.4→v4.5 迁移，绝不从 `tasks.json` 回退或直接改投影。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | task id | 拓扑序第一个 `pending` |
-
-## Workflow
-
-完整 8 步流程见 `@skills/ultra-dev/SKILL.md`（Resume Check → Design Gate → 选 task →
-状态 in_progress → 环境 → TDD → 质量门 → checkpoint → review → 完成 → commit/merge → report）。
-
-**命令入口做的事**：
-1. 读 `.ultra/workflow-state.json` 决定新跑 vs resume
-2. 首跑通过 Host 原生提问触发 Design Approval Gate
-3. 驱动 skill 走 TDD + review 循环；状态仅通过 MCP `task.update`
-4. task 有 `change_id` 时把需求变化写进 active delta，并用 `change.context` 刷新上下文
-5. Step 4.5 review 通过 `/ultra-review` 和 Host 原生 subagent 执行
-6. Step 4.4 pre-review checkpoint 写入 workflow-state.json，不依赖 `/compact`
-
-## 用法
-
-```bash
-/ultra-dev          # 自动选下一个 pending task
-/ultra-dev 3        # 直接做 task 3
-```
-
-## 下一步
-
-单个 task 完成后自动提示下一个 `/ultra-dev`；所有 Walking Skeleton +
-critical-path task 完成 → `/ultra-test` 做交付前质量审计。
+Read and follow `@skills/ultra-dev/SKILL.md`, using `$ARGUMENTS` as the optional task id.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-doctor.md

@@ -1,36 +1,10 @@
 ---
-description: Inspect Ultra runtime health and optionally run explicit backup-first mechanical recovery
+description: Diagnose Ultra state and installed-plugin health with optional explicit repair
 argument-hint: "[--repair]"
-allowed-tools: Read, Bash
-model: opus
 workflow-ref: "@skills/ultra-doctor/SKILL.md"
-mcp_tools_required:
-  - system.doctor
-cli_fallback: "system doctor"
 ---
 
-# /ultra-doctor
+# Diagnose Ultra health
 
-## 目标
-
-诊断 state.db、projection、incident、session 和 active change artifact 的健康状态。
-默认只读；只有显式传入 `--repair` 才允许备份后执行机械恢复。
-
-## Workflow
-
-完整契约见 `@skills/ultra-doctor/SKILL.md`。
-
-1. 默认调用 `system.doctor {"repair": false}`。
-2. 只报告失败检查、incident、游标落后和归属边界。
-3. `--repair` 时必须先生成 state.db 备份，再恢复 orphan、消费 staleness event、
-   重排超时中断或失败的 projection 并重新投影。
-4. 修复后重新读取报告；仍 degraded 就明确剩余阻塞，不宣称完成。
-
-## 用法
-
-```bash
-/ultra-doctor
-/ultra-doctor --repair
-```
-
-Memory 和代码图谱属于外部 provider，本命令既不收集也不修复它们。
+Read and follow `@skills/ultra-doctor/SKILL.md`; allow repair only when `$ARGUMENTS` explicitly contains `--repair`.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-init.md

@@ -1,52 +1,10 @@
 ---
-description: Initialize Ultra Builder Pro project — scaffold .ultra/, initialize state.db and continuous-change directories, optional git
-argument-hint: <name> <type> <stack> [git]
-allowed-tools: Read, Write, Bash, Grep, Glob, AskUserQuestion
-model: opus
+description: Initialize an Ultra project with authoritative state and baseline specification files
+argument-hint: "[name] [type] [stack] [git]"
 workflow-ref: "@skills/ultra-init/SKILL.md"
-mcp_tools_required:
-  - task.init_project
-cli_fallback: "task init-project"
 ---
 
-# /ultra-init
+# Initialize an Ultra project
 
-## 目标
-
-搭 `.ultra/` 骨架（specs + tasks + changes + docs + reports），初始化权威
-`state.db`，写入带元数据的初始 `tasks.json`，并按需初始化 git。Claude Code、
-OpenCode、Codex 三个 runtime 行为一致。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | 项目名 | 当前目录名 |
-| `$2` | 项目类型（`web`/`api`/`cli`/`fullstack`/`other`） | 从 package 文件识别 |
-| `$3` | 技术栈（逗号分隔） | 从 package 文件识别 |
-| `$4` | `git` → 初始化 git | 检测已有 `.git/` 时询问 |
-
-## Workflow
-
-完整流程见 `@skills/ultra-init/SKILL.md`（4 步：状态检测 → 参数补全 →
-`task.init_project` 拉起骨架 → git 集成）。
-
-**命令入口做的事**：
-1. 解析 `$1-$4`，补缺省
-2. 探测 runtime 能力：优先走 MCP `task.init_project`；不可达时退回 `ultra-tools task init-project`
-3. 按 skill 的 4 步工作流推进
-4. 完成后提示下一步命令
-
-## 用法
-
-```bash
-/ultra-init                          # 交互模式（自动识别）
-/ultra-init my-app                   # 带项目名
-/ultra-init my-app api               # 带类型
-/ultra-init my-app fullstack react,postgres git  # 完整 + git
-```
-
-## 下一步
-
-**CRITICAL**：跑 `/ultra-research` 做 17 步 discovery 把 spec 填满，
-**然后**才跑 `/ultra-plan` 生成任务。直接 plan 会产出基于模糊需求的任务。
+Read and follow `@skills/ultra-init/SKILL.md`, using `$ARGUMENTS` as optional project metadata.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-plan.md

@@ -1,53 +1,10 @@
 ---
-description: Generate task breakdown from complete specs — walking-skeleton first, vertical slices, via MCP task.create
-argument-hint: [scope]
-allowed-tools: Read, Write, Edit, Bash(mkdir .ultra/*), Grep, Glob, AskUserQuestion
-model: opus
+description: Convert validated requirements into dependency-valid Ultra tasks with bounded context and exact verification
+argument-hint: "[scope]"
 workflow-ref: "@skills/ultra-plan/SKILL.md"
-mcp_tools_required:
-  - task.create
 ---
 
-# /ultra-plan
+# Plan executable slices
 
-## 目标
-
-把 `/ultra-research` 验证过的完整 spec 转成可执行的任务计划：先 Walking
-Skeleton 贯穿所有层，再切 vertical slices，每 3-4 个 feature task 插一个
-Integration Checkpoint。任务写入 state.db（MCP `task.create`），projector
-自动生成 `.ultra/tasks/tasks.json` + contexts/*.md frontmatter。
-
-入口先写 active `.ultra/workflow-state.json`。MCP 不可用或返回
-`LEGACY_STATE_MIGRATION_REQUIRED` 时立即停止，提示运行
-`ultra-tools migrate --from=4.4 --to=4.5 --source-dir <project-root>`；绝不读取或写入
-`tasks.json` 作为回退。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | scope 模式（EXPAND / SELECTIVE / HOLD / REDUCE） | 询问用户；默认 SELECTIVE |
-
-## Workflow
-
-完整 8 步流程见 `@skills/ultra-plan/SKILL.md`。
-
-**命令入口做的事**：
-1. 探测 spec 完整度 — 未填充则 block 并转 `/ultra-research`
-2. 使用 Host 原生提问界面交互选 scope 模式
-3. 驱动 skill 跑生成 → 依赖分析 → `task.create` 循环 → 写 context-md 正文
-4. 跑 7 项 verification（requirement coverage / 无环 / trace_to / 复杂度等）
-5. 输出 report + 下一步
-
-## 用法
-
-```bash
-/ultra-plan                 # 交互模式；默认 SELECTIVE
-/ultra-plan EXPAND          # 直接进入"激进扩张"模式
-/ultra-plan REDUCE          # MVP 最小化模式
-```
-
-## 下一步
-
-所有 CRITICAL check 过了 → `/clear` 然后 `/ultra-dev` 开始 TDD。
-单个 task 完成后 `/ultra-status` 看进度。
+Read and follow `@skills/ultra-plan/SKILL.md`, using `$ARGUMENTS` to select the requested scope.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-research.md

@@ -1,59 +1,10 @@
 ---
-description: Think-Driven Interactive Discovery — 17-step research with per-step web search and spec-file output
-argument-hint: [topic]
-allowed-tools: Task, Read, Write, WebSearch, WebFetch, Grep, Glob, AskUserQuestion
-model: opus
+description: Research unresolved product or architecture decisions and update the authoritative baseline specifications
+argument-hint: "[scope-or-question]"
 workflow-ref: "@skills/ultra-research/SKILL.md"
 ---
 
-# Ultra Research v2
+# Research a baseline
 
-**Step-file architecture**: Each research step is a self-contained instruction file loaded just-in-time for maximum LLM attention density.
-
-## How This Works
-
-1. Read the main skill file: `skills/ultra-research/SKILL.md`
-2. Follow the activation sequence (pre-checks → project type detection → step routing)
-3. For each step: Read `skills/ultra-research/steps/step-{NN}-{name}.md` and follow ALL instructions
-4. Each step writes output immediately to spec files, then presents [C] Continue gate
-5. Only proceed to next step after user confirms [C]
-
-## Step Sequence
-
-| Step | File | Focus |
-|------|------|-------|
-| **R0: Product Discovery** | | |
-| 00 | `step-00-problem-validation.md` | Validate the problem is real |
-| 01 | `step-01-opportunity-discovery.md` | Map opportunity space (OST) |
-| 02 | `step-02-market-assessment.md` | TAM/SAM/SOM sizing |
-| 03 | `step-03-competitive-landscape.md` | Competitor analysis |
-| 04 | `step-04-product-strategy.md` | Vision, segments, trade-offs |
-| 05 | `step-05-assumptions-validation.md` | Risk assumptions + experiments |
-| **R1: User & Scenario** | | |
-| 10 | `step-10-user-personas.md` | 2-3 personas |
-| 11 | `step-11-user-scenarios.md` | 3-5 user scenarios |
-| **R2: Feature Definition** | | |
-| 20 | `step-20-user-stories.md` | Stories + acceptance criteria |
-| 21 | `step-21-features-scope.md` | MVP scope + exclusions |
-| 22 | `step-22-success-metrics.md` | KPIs + targets |
-| **R3: Architecture** | | |
-| 30 | `step-30-architecture-context.md` | Quality goals, constraints |
-| 31 | `step-31-solution-strategy.md` | Tech stack decisions |
-| 32 | `step-32-building-blocks.md` | Modules + runtime scenarios |
-| **R4: Quality & Deploy** | | |
-| 40 | `step-40-deployment.md` | Infrastructure + CI/CD |
-| 41 | `step-41-quality-risks.md` | Quality scenarios + risks |
-| **Synthesis** | | |
-| 99 | `step-99-synthesis.md` | Distillate + validation |
-
-## Critical Rules
-
-- **Read SKILL.md first** — it has activation logic and project type detection
-- **One step at a time** — never load multiple step files simultaneously
-- **Write immediately** — every step writes to spec file before presenting to user
-- **Web search mandatory** — factual claims need sources, no exceptions
-- **User gate** — halt at [C] Continue, do not auto-proceed
-
-## Begin
-
-Read `skills/ultra-research/SKILL.md` now and follow the activation sequence.
+Read and follow `@skills/ultra-research/SKILL.md`, using `$ARGUMENTS` to bound the research scope.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-status.md

@@ -1,49 +1,10 @@
 ---
-description: Real-time project status — progress + risks + workflow routing, via MCP task.list
-argument-hint: "[task-id]"
-allowed-tools: Read, Bash(git status), Bash(git log *), Grep, Glob, Task
-model: opus
+description: Report authoritative Ultra health, readiness, evidence freshness, and one next action
+argument-hint: "[task-or-change-id]"
 workflow-ref: "@skills/ultra-status/SKILL.md"
-mcp_tools_required:
-  - task.list
-  - task.get
-  - change.list
-  - system.doctor
 ---
 
-# /ultra-status
+# Report Ultra status
 
-## 目标
-
-一次调用拿整个项目近况：任务进度（来自 state.db `task.list`）+ 测试状态（`test-report.json`）+
-发布状态（`delivery-report.json`）+ active change + runtime health + 下一步命令路由。只读。
-任务状态只接受 MCP `task.list`/`task.get`；失败时原样报告并停止，绝不读取
-`tasks.json` 冒充权威数据。旧 v4.4 数据必须先执行正式迁移。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | 单 task id（只看这个 task） | 不填 → 全局报告 |
-
-## Workflow
-
-完整 5 阶段见 `@skills/ultra-status/SKILL.md`（validation → load → progress → risk → routing）。
-
-**命令入口做的事**：
-1. 环境检查（state.db 可达 + 有 task）
-2. `task.list` + `change.list` + read-only `system.doctor`；读 test/delivery report
-3. 算进度 + 风险（含 projection、incident、context/docs drift）
-4. 初始交付后不再显示终局 Done；健康 baseline 的下一项日常工作路由到 `/ultra-change`
-
-## 用法
-
-```bash
-/ultra-status            # 项目全局报告
-/ultra-status 3          # 只看 task 3
-```
-
-## 下一步
-
-看输出的 `▶ Next Up` 块。常见场景：有 pending → `/ultra-dev`；全绿 → `/ultra-test`；
-test passed → `/ultra-deliver`；已归档且 baseline 健康 → `/ultra-change`。
+Read and follow `@skills/ultra-status/SKILL.md`, using `$ARGUMENTS` to select a specific task or change.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-test.md

@@ -1,50 +1,10 @@
 ---
-description: Pre-delivery quality audit — Anti-Pattern + Coverage Gap + Wiring + E2E + Perf + Security
-argument-hint: [scope]
-allowed-tools: Bash, Read, Write, Edit, Task, Grep, Glob, AskUserQuestion
-model: opus
+description: Run the independent pre-delivery verification gate and record current acceptance evidence
+argument-hint: "[scope]"
 workflow-ref: "@skills/ultra-test/SKILL.md"
-mcp_tools_required:
-  - task.list
-  - change.list
 ---
 
-# /ultra-test
+# Verify delivery readiness
 
-## 目标
-
-`/ultra-deliver` 前的项目级质量审计：6 类 gate（Anti-Pattern / Coverage Gap /
-Wiring / E2E / Performance / Security）× auto-fix loop。**只读** state.db，
-写 `.ultra/test-report.json` 作为 `/ultra-deliver` 的准入凭证。
-completed-task 前置检查必须来自 MCP `task.list`；失败时停止，绝不回退到
-`tasks.json`。`LEGACY_STATE_MIGRATION_REQUIRED` 必须先完成 v4.4→v4.5 迁移。
-
-**注意**：这不是跑单测（那是 `/ultra-dev`）。这是交付前的体检。
-
-## 参数
-
-| 位 | 含义 | 缺省 |
-|----|------|------|
-| `$1` | 审计范围（`all`/`anti-pattern`/`coverage`/`e2e`/`perf`/`security`） | `all` |
-
-## Workflow
-
-完整 8 步见 `@skills/ultra-test/SKILL.md`（pre-check → 6 gates → auto-fix → persist → report）。
-
-**命令入口做的事**：
-1. 探测项目类型 + `task.list` 确认 ≥1 completed
-2. 按 scope 跑 gates；失败进 auto-fix（最多 5 轮）
-3. 写 `.ultra/test-report.json`（change_id + exact commands + gate 明细 + blocking_issues）
-4. 通过 → 提示 `/ultra-deliver`
-
-## 用法
-
-```bash
-/ultra-test                # 全量审计
-/ultra-test security       # 只跑安全审计
-/ultra-test coverage       # 只找覆盖缺口
-```
-
-## 下一步
-
-`passed=true` → `/ultra-deliver`；`passed=false` → 修或跟进 `blocking_issues`。
+Read and follow `@skills/ultra-test/SKILL.md`, using `$ARGUMENTS` to bound the verification scope.
+Treat the referenced skill as the only workflow definition.

package/commands/ultra-think.md

@@ -1,45 +1,10 @@
 ---
-description: Deep analysis with adversarial reasoning — Evidence-First + Multi-Perspective + Stress-Test + Confidence-Quantified recommendation
-argument-hint: "[problem or decision to analyze]"
-allowed-tools: Read, Grep, Glob, Bash, Write, Task, WebSearch, WebFetch, AskUserQuestion, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa, mcp__context7__resolve-library-id, mcp__context7__query-docs
-model: opus
+description: Analyze a consequential question with evidence, uncertainty, and proportionate stress testing
+argument-hint: "[question]"
 workflow-ref: "@skills/ultra-think/SKILL.md"
-cli_fallback: "direct user interaction"
 ---
 
-# /ultra-think
+# Analyze a consequential question
 
-## 目标
-
-结构化深度分析复杂问题/决策/诊断。Evidence-First 标注（Fact/Inference/Speculation）+
-多视角 + 对抗压测（Steel-Man / Pre-Mortem / Sensitivity / Second-Order）→
-量化置信度的推荐 + 验证计划。
-
-## 参数
-
-<problem>
-$ARGUMENTS
-</problem>
-
-## Workflow
-
-完整 5 步见 `@skills/ultra-think/SKILL.md`（Scope → Evidence → Multi-Perspective →
-Adversarial → Synthesis）。
-
-**命令入口做的事**：
-1. 读 `$ARGUMENTS` 判定问题范围 — 模糊 → 用 Host 原生提问界面最多澄清 3 个问题
-2. 简单问题 → 直接答；复杂 → 跑完整框架
-3. 输出 Markdown 报告（Problem / Analysis / Options / Adversarial / Recommendation /
-   Verification / Next Steps）
-
-## 用法
-
-```bash
-/ultra-think "should we switch from REST to gRPC for the internal API?"
-/ultra-think "why is the deploy pipeline flaky every 3rd run?"
-```
-
-## 下一步
-
-方案进入 spec → `/ultra-research` 补证据或 `/ultra-plan` 直接排任务；
-纯诊断 → 跟着 Verification Plan 走，取证后再定。
+Read and follow `@skills/ultra-think/SKILL.md`, treating `$ARGUMENTS` as the question to resolve.
+Treat the referenced skill as the only workflow definition.

package/docs/PLAN.zh-CN.md

@@ -10,9 +10,9 @@
 > Kimi Code 采用各自 native plugin 呈现，其他旧 runtime adapter 已退役。下文所有与此冲突的
 > memory/hindsight 章节仅作为历史实施记录，不再是当前需求或运行时契约。
 
-**当前状态**：v0.10.0；四宿主 native plugin、32 个 live MCP tool、
-schema 10.0（16 表）、Context Spine v2 / breadcrumb / spec-learning、持续
-change/context/convergence/doctor、incident debug lane、
+**当前状态**：v0.11.0；四宿主 native plugin、32 个 live MCP tool、
+schema 10.0（16 表）、portable Skill authoring contract、双轴 review、
+Context Spine v2 / breadcrumb / spec-learning、持续 change/context/convergence/doctor、incident debug lane、
 checkpoint 恢复消费与跨宿主安装 provenance/doctor 已落地；npm 发布由
 `v*.*.*` tag 触发。以下 Phase 0-9 正文保留为 2026-04 的实施历史，不再作为
 当前 runtime 或发布状态的事实来源。

package/docs/ROADMAP.md

@@ -13,7 +13,7 @@ sharing one authoritative workflow store.
 
 **Distribution channels (v1.0)**: npm · Homebrew · pip.
 
-**Release line**: `0.10.x`; every release is gated by `npm run verify:release`.
+**Release line**: `0.11.x`; every release is gated by `npm run verify:release`.
 
 ---
 

package/docs/SKILL-AUTHORING.md

@@ -0,0 +1,75 @@
+# Skill authoring contract
+
+Ultra Builder Pro keeps one portable source workflow and adapts only runtime metadata
+or host invocation details. This contract follows OpenAI Skills guidance and the Agent
+Skills progressive-disclosure format:
+
+- <https://learn.chatgpt.com/docs/build-skills>
+- <https://learn.chatgpt.com/docs/customization/overview>
+- <https://agentskills.io/specification>
+- <https://agentskills.io/skill-creation/best-practices>
+
+## Surface ownership
+
+| Content | Owner |
+|---|---|
+| Repeatable task procedure and conditional references | `skills/<name>/SKILL.md` |
+| Codex display, invocation policy, and dependencies | `skills/<name>/agents/openai.yaml` after adaptation |
+| Host launcher | `commands/<name>.md` |
+| Durable repository or user engineering policy | `AGENTS.md` or the host equivalent |
+| Deterministic lifecycle enforcement | one hook implementation |
+| Live external data or actions | MCP server or connector |
+| Bounded delegated role | `agents/<name>.md` |
+
+Do not duplicate a rule across these surfaces.
+
+## Portable `SKILL.md`
+
+Source frontmatter contains only `name` and `description`. The description says what
+the Skill does and when it should activate. The body uses imperative, outcome-oriented
+steps and includes only information an agent cannot reliably infer from the task,
+repository, or host policy.
+
+Keep the main file compact. Move conditional domain detail to `references/`, reusable
+deterministic work to `scripts/`, and output material to `assets/`. Reference a file
+only from the main workflow or one directly relevant reference.
+
+## Language
+
+The standards do not prohibit Chinese. Ultra source prompts use English as a project
+policy because one source is transformed for Claude Code, Codex, OpenCode, and Kimi
+Code. The host or user instruction controls the response language; a workflow must not
+hard-code the user's output language unless language is itself part of the task.
+
+Maintainer documentation may use the language appropriate for its audience. English
+source prompts are a portability rule, not a claim that multilingual Skills are invalid.
+
+## Content that does not belong in a Skill prompt
+
+- release notes, migration history, old-version behavior, or implementation diary;
+- host tool inventories, model pins, package paths, and dependency metadata shared by
+  only one runtime;
+- generic engineering doctrine already owned by user or repository instructions;
+- one-off project facts, volatile external facts, or copied datasets;
+- duplicated command bodies, hook policy, MCP schemas, or private memory behavior;
+- arbitrary coverage, confidence, complexity, option-count, or severity thresholds;
+- pattern matching that turns TODOs, mocks, catch blocks, or line counts directly into
+  findings without a reachable impact;
+- tutorial-style old/new or good/bad comparisons that do not change the workflow;
+- menus of hypothetical alternatives when one repository default already satisfies the
+  contract.
+
+Comparison is appropriate only when the task requires a real decision or verification:
+compare credible alternatives against shared constraints, accepted specification
+against delivered behavior, or independent analyses against authoritative evidence.
+
+## Review checklist
+
+1. Does the description state a precise use condition?
+2. Is every instruction reusable for this Skill rather than copied global policy?
+3. Is host-specific metadata outside the portable prompt?
+4. Does each conditional reference earn its context cost?
+5. Are judgments evidence-based rather than threshold-based?
+6. Are commands thin and agents bounded?
+7. Do positive and negative trigger evals cover accidental activation?
+8. Do source, four generated runtimes, and package contents pass validation?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ultra-builder-pro-cli",
-  "version": "0.10.0",
+  "version": "0.11.0",
   "description": "Multi-runtime installer for the Ultra Builder Pro agent engineering system — deploys commands, agents, skills, hooks, and MCP server to Claude Code, OpenCode, Codex CLI, and Kimi Code.",
   "bin": {
     "ultra-builder-pro-cli": "bin/install.js",
@@ -50,6 +50,7 @@
     "docs/ROADMAP.md",
     "docs/ARCHITECTURE.md",
     "docs/AGENT-CONTEXT.md",
+    "docs/SKILL-AUTHORING.md",
     "docs/COMMIT-HASH-BACKFILL.md",
     "docs/PLAN.zh-CN.md",
     "docs/STATE-DB-ACCESS-POLICY.md",
@@ -87,7 +88,7 @@
     "test:state": "node --test 'mcp-server/**/*.test.cjs'",
     "test:orch": "node --test 'orchestrator/**/*.test.cjs'",
     "test:spec": "node spec/scripts/test-all.cjs",
-    "test:rest": "node --test adapters/_shared/tests/*.test.cjs adapters/tests/*.test.cjs ultra-tools/*.test.cjs tests/conformance/**/*.test.cjs tests/install.test.cjs tests/package-smoke.test.cjs tests/retired-runtime.test.cjs",
+    "test:rest": "node --test adapters/_shared/tests/*.test.cjs adapters/tests/*.test.cjs ultra-tools/*.test.cjs tests/conformance/**/*.test.cjs tests/*.test.cjs",
     "test:all": "npm run test:state && npm run test:orch && npm run test:spec && npm run test:rest",
     "test:hooks": "pytest hooks/tests -q",
     "verify:release": "npm run test:all && npm run test:hooks && npm audit --omit=dev --audit-level=high",