@ai-content-space/loopx 0.1.4 → 0.1.6

package/README.md

@@ -25,10 +25,12 @@ clarify -> plan -> build -> review -> approve review->done -> archive
 ## Features
 
 - Installs and exposes eleven bundled loopx Codex skills: workflow skills `clarify`, `plan`, `build`, `review`, `archive`, and `autopilot`; quality support skills `debug`, `tdd`, and `verify`; and Go support skills `go-style` and `kratos`.
+- Keeps bundled skill routing explicit in `skills/RESOLVER.md`, with deterministic governance checks for frontmatter, plugin mirrors, resolver coverage, local references, package inclusion, and version alignment.
 - Supports npm global install and Codex plugin install through the same install/discovery core.
 - Installs a managed Codex workflow hook that surfaces loopx workflow state and safe next-action hints inside Codex.
 - Stores runtime state and stage artifacts locally under `.loopx/` for auditability, recovery, and migration.
 - Stores clarify intake snapshots under `.loopx/intake/` so `.loopx/specs/` stays reserved for long-lived domain specs.
+- Records existing project AI rule files, existing spec sources, and detected verification commands in `.loopx/config.json` during init so loopx can preserve local sources of truth while still running the full workflow.
 - Runs `plan` with a Planner -> Architect -> Critic consensus loop by default.
 - Writes OpenSpec-inspired change artifacts during `plan`: proposal, spec delta, design, vertical slices, tasks, and an artifact dependency graph.
 - Provides per-repo agent context under `.loopx/agents/` and `.loopx/context/domain.md`, consumed by build/review context manifests.
@@ -138,7 +140,15 @@ loopx status my-task
 loopx status my-task --json
 ```
 
-Render derived HTML reading views:
+Planning also writes derived HTML reading views so the plan can be reviewed without another command:
+
+```text
+.loopx/workflows/my-task/view/index.html
+.loopx/workflows/my-task/view/plan.html
+.loopx/views/index.html
+```
+
+Regenerate derived HTML reading views at any time:
 
 ```bash
 loopx render my-task
@@ -172,7 +182,25 @@ loopx repair-install
 
 The CLI is primarily for runtime, debugging, status inspection, and maintenance. The normal Codex-facing product surface is the bundled skill set, for example `$clarify`, `$plan`, `$build`, `$review`, `$archive`, `$autopilot`, `$debug`, `$tdd`, `$verify`, `$go-style`, and `$kratos`.
 
-`loopx status` remains a CLI/runtime diagnostic command rather than a Codex skill. `loopx render` generates human-readable HTML views from existing runtime artifacts; without a slug it renders every non-legacy workflow plus the workspace index. Markdown and JSON remain the canonical machine-readable and editable sources.
+`loopx status` remains a CLI/runtime diagnostic command rather than a Codex skill. `loopx plan` automatically writes human-readable HTML views for the planned workflow and workspace index. `loopx render` regenerates those views from existing runtime artifacts; without a slug it renders every non-legacy workflow plus the workspace index. Markdown and JSON remain the canonical machine-readable and editable sources.
+
+## Skill Routing and Governance
+
+The bundled skill resolver lives at:
+
+```text
+skills/RESOLVER.md
+```
+
+It is the human-readable routing map for the eleven bundled skills. Keep it aligned with each `skills/<name>/SKILL.md` and mirrored `plugins/loopx/skills/<name>/SKILL.md`.
+
+Skill governance is enforced by:
+
+```bash
+node scripts/verify-skills.mjs
+```
+
+The verifier checks that bundled skill frontmatter is triggerable and bounded, `metadata.version` matches `package.json`, plugin skill mirrors match the canonical skills, `skills/RESOLVER.md` covers every bundled skill without stale bundled-skill references, local skill references exist, the plugin manifest version matches the package version, and the verifier itself is included in the npm package.
 
 ## Skills
 
@@ -204,6 +232,8 @@ Main artifacts:
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 
+After a successful plan run, loopx also writes derived reading views at `.loopx/workflows/<slug>/view/index.html`, `.loopx/workflows/<slug>/view/plan.html`, and `.loopx/views/index.html`. Use these for human review; keep Markdown and JSON as the editable sources of truth.
+
 `spec-delta.md` uses requirement deltas: `## ADDED Requirements`, `## MODIFIED Requirements`, `## REMOVED Requirements`, and `## RENAMED Requirements`. ADDED and MODIFIED entries are full `### Requirement:` blocks with SHALL/MUST language and `#### Scenario:` examples, so archive can merge them into the current long-lived spec state.
 
 ### build
@@ -337,14 +367,17 @@ loopx writes runtime state under `.loopx/` in the current project:
         review.html
       plan-reviews/
       build-support/
+      review-support/
   autopilot/
     <slug>/
       run.json
 ```
 
+`config.json` records the loopx product contract plus init-time project discovery: existing AI rules such as `AGENTS.md` / `CLAUDE.md` / Cursor / Copilot files, existing spec sources such as `docs/changes` or ADR/RFC folders, and detected install/test/lint/typecheck/build/E2E commands. This does not create a lighter loopx mode; it keeps project facts available to `plan`, `build`, and `review` while preserving loopx's full closed workflow.
+
 `intake` contains immutable clarify snapshots for a specific request. `workflows` contains the active runtime working set. `changes` contains the proposed change delta for the current request. `specs` contains accepted long-lived behavior after archive.
 
-`views/` and `workflows/<slug>/view/` are derived HTML reading views generated by `loopx render`. They are for human review only and are safe to regenerate; agents and tooling should continue to read and update the Markdown and JSON artifacts.
+`views/` and `workflows/<slug>/view/` are derived HTML reading views written after `plan` and regenerated by `loopx render`. They are for human review only and are safe to regenerate; agents and tooling should continue to read and update the Markdown and JSON artifacts.
 
 ### Document Boundaries
 
@@ -354,11 +387,12 @@ Documents users normally need to watch:
 - `.loopx/workflows/<slug>/spec.md`: the current requirement working copy.
 - `.loopx/workflows/<slug>/plan.md`, `architecture.md`, `development-plan.md`, and `test-plan.md`: the current task's plan, architecture, execution, and verification contract.
 - `.loopx/workflows/<slug>/execution-record.md` and `review-report.md`: execution evidence and review result.
-- `.loopx/views/index.html` and `.loopx/workflows/<slug>/view/index.html`: reading entrypoints generated by `loopx render`.
+- `.loopx/views/index.html` and `.loopx/workflows/<slug>/view/index.html`: reading entrypoints written after `plan` and regenerated by `loopx render`.
 
 Documents users may read and modify as workflow fact sources:
 
 - `.loopx/workflows/<slug>/*.md`: editable working-copy artifacts for the active workflow; changes still need to pass the relevant stage gates.
+- `.loopx/config.json`: workspace configuration, project-rule/spec-source discovery, and default verification commands; update it if the repository's canonical commands or project-rule files change.
 - `.loopx/context/domain.md` and `.loopx/agents/*.md`: project context, domain vocabulary, and agent collaboration guidance.
 - `.loopx/changes/active/<change-id>/*.md`: plan-generated change proposal, design, tasks, and spec delta; edits should be followed by plan/build/review validation.
 - `.loopx/specs/<domain>/spec.md`: long-lived archived behavior specs; normally synced by `archive`, and manual edits should stay consistent with later change deltas.
@@ -370,7 +404,7 @@ Documents and data the tools depend on, or generate as derived evidence:
 - `.loopx/intake/clarify-*.md`: immutable clarify snapshots for audit and traceability; do not treat them as long-lived specs.
 - `.loopx/changes/active/<change-id>/slices.json` and `artifact-graph.json`: structured planning data consumed by build/review/archive.
 - `.loopx/autopilot/<slug>/run.json` and `.loopx/build-active.json`: orchestration and stop-hook runtime state.
-- `.loopx/views/` and `.loopx/workflows/<slug>/view/`: derived HTML views; they can be deleted and regenerated with `loopx render`, and should not be edited as fact sources.
+- `.loopx/views/` and `.loopx/workflows/<slug>/view/`: derived HTML views; they are written after `plan`, can be deleted and regenerated with `loopx render`, and should not be edited as fact sources.
 
 ## Diagnostics and Repair
 
@@ -392,6 +426,12 @@ Check skill discovery state only:
 node scripts/install-skills.mjs --check
 ```
 
+Verify bundled skill governance:
+
+```bash
+node scripts/verify-skills.mjs
+```
+
 ## Codex Workflow Hook
 
 `install-skills.mjs` and the Codex plugin installer automatically install `scripts/codex-workflow-hook.mjs` to:
@@ -443,9 +483,17 @@ Run tests:
 npm test
 ```
 
+`npm test` runs bundled skill governance first, then the Node test suites:
+
+```bash
+node scripts/verify-skills.mjs
+node --test test/*.test.mjs
+```
+
 Useful verification commands:
 
 ```bash
+node scripts/verify-skills.mjs
 node --test test/*.test.mjs
 node scripts/install-skills.mjs --check
 node --test plugins/loopx/scripts/plugin-install.test.mjs
@@ -462,6 +510,7 @@ node src/cli.mjs status --json
 - `README.zh-CN.md`
 - `package.json`
 - `scripts/install-skills.mjs`
+- `scripts/verify-skills.mjs`
 - `scripts/codex-stop-hook.mjs`
 - `scripts/codex-workflow-hook.mjs`
 - `assets/logo.svg`
@@ -472,4 +521,4 @@ node src/cli.mjs status --json
 
 ## Version
 
-Current npm package version: `0.1.4`.
+Current npm package version: `0.1.6`.

package/README.zh-CN.md

@@ -27,10 +27,12 @@ clarify -> plan -> build -> review -> approve review->done -> archive
 ## 特性
 
 - 安装并公开 11 个 loopx Codex skills：工作流 skills `clarify`、`plan`、`build`、`review`、`archive`、`autopilot`，质量辅助 skills `debug`、`tdd`、`verify`，以及 Go 支持 skills `go-style`、`kratos`。
+- 通过 `skills/RESOLVER.md` 明确 bundled skill 路由，并用确定性治理脚本检查 frontmatter、plugin 镜像、resolver 覆盖、本地引用、发布包包含项和版本一致性。
 - 支持 npm 全局安装和 Codex plugin 安装，两种安装方式共享同一套 install/discovery 逻辑。
 - 自动安装 loopx 管理的 Codex workflow hook，在 Codex 中提示当前 workflow 状态和安全下一步。
 - 所有运行时状态和阶段产物都写入项目本地 `.loopx/`，便于审计、恢复和迁移。
 - clarify 需求快照写入 `.loopx/intake/`，让 `.loopx/specs/` 只承载长期领域规格。
+- init 时会把已有项目 AI 规则、既有 spec 来源和自动发现的验证命令记录到 `.loopx/config.json`，让 loopx 保留项目原有事实源，同时继续执行完整闭环。
 - `plan` 默认采用 Planner -> Architect -> Critic 的共识规划循环。
 - `plan` 会写入借鉴 OpenSpec 的 change artifacts：proposal、spec delta、design、tasks 和 artifact dependency graph。
 - 提供项目级 agent context：`.loopx/agents/` 和 `.loopx/context/domain.md`，供 build/review 的 context manifest 消费。
@@ -140,7 +142,15 @@ loopx status my-task
 loopx status my-task --json
 ```
 
-生成派生 HTML 阅读视图：
+plan 完成后会自动写入派生 HTML 阅读视图，方便直接审阅计划：
+
+```text
+.loopx/workflows/my-task/view/index.html
+.loopx/workflows/my-task/view/plan.html
+.loopx/views/index.html
+```
+
+需要时也可以重新生成派生 HTML 阅读视图：
 
 ```bash
 loopx render my-task
@@ -174,7 +184,25 @@ loopx repair-install
 
 CLI 主要用于运行时、调试、状态观察和维护。日常面向 Codex 的主入口是同名 skills，例如 `$clarify`、`$plan`、`$build`、`$review`、`$archive`、`$autopilot`、`$debug`、`$tdd`、`$verify`、`$go-style`、`$kratos`。
 
-`loopx status` 仍然是 CLI/runtime 诊断命令，不作为单独 Codex skill 暴露。`loopx render` 会基于现有运行时产物生成给人阅读的 HTML 视图；不传 slug 时会渲染所有非 legacy workflow 和工作区首页。Markdown 和 JSON 仍然是机器可读、可编辑的事实源。
+`loopx status` 仍然是 CLI/runtime 诊断命令，不作为单独 Codex skill 暴露。`loopx plan` 会自动为当前计划 workflow 和工作区首页写入给人阅读的 HTML 视图。`loopx render` 会基于现有运行时产物重新生成这些视图；不传 slug 时会渲染所有非 legacy workflow 和工作区首页。Markdown 和 JSON 仍然是机器可读、可编辑的事实源。
+
+## Skill 路由与治理
+
+bundled skill resolver 位于：
+
+```text
+skills/RESOLVER.md
+```
+
+它是 11 个 bundled skills 的可读路由表。修改任一 `skills/<name>/SKILL.md` 或镜像的 `plugins/loopx/skills/<name>/SKILL.md` 时，都要保持 resolver 同步。
+
+skill 治理由下面的确定性脚本执行：
+
+```bash
+node scripts/verify-skills.mjs
+```
+
+该脚本会检查 bundled skill frontmatter 是否可触发且有排除边界、`metadata.version` 是否匹配 `package.json`、plugin skill 镜像是否与 canonical skills 一致、`skills/RESOLVER.md` 是否覆盖所有 bundled skills 且没有陈旧 bundled-skill 引用、本地 skill 引用是否存在、plugin manifest 版本是否匹配 package 版本，以及 verifier 本身是否进入 npm 发布包。
 
 ## Skill 说明
 
@@ -199,12 +227,15 @@ CLI 主要用于运行时、调试、状态观察和维护。日常面向 Codex
 - `.loopx/changes/active/<change-id>/spec-delta.md`
 - `.loopx/changes/active/<change-id>/design.md`
 - `.loopx/changes/active/<change-id>/tasks.md`
+- `.loopx/changes/active/<change-id>/slices.json`
 - `.loopx/changes/active/<change-id>/artifact-graph.json`
 - `.loopx/workflows/<slug>/plan.md`
 - `.loopx/workflows/<slug>/architecture.md`
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 
+plan 成功后，loopx 还会写入派生阅读视图：`.loopx/workflows/<slug>/view/index.html`、`.loopx/workflows/<slug>/view/plan.html` 和 `.loopx/views/index.html`。这些视图用于人工审阅；Markdown 和 JSON 仍然是可编辑事实源。
+
 `spec-delta.md` 使用 requirement delta：`## ADDED Requirements`、`## MODIFIED Requirements`、`## REMOVED Requirements` 和 `## RENAMED Requirements`。ADDED / MODIFIED 必须是完整的 `### Requirement:` 块，包含 SHALL/MUST 约束和 `#### Scenario:` 场景，archive 才能把它们合并进长期 spec 当前状态。
 
 ### build
@@ -347,14 +378,17 @@ loopx 在当前项目下写入 `.loopx/`：
         review.html
       plan-reviews/
       build-support/
+      review-support/
   autopilot/
     <slug>/
       run.json
 ```
 
+`config.json` 记录 loopx 产品契约和 init 时的项目发现结果：已有 AI 规则文件，例如 `AGENTS.md`、`CLAUDE.md`、Cursor / Copilot 规则；已有 spec 来源，例如 `docs/changes`、ADR/RFC 目录；以及自动发现的 install/test/lint/typecheck/build/E2E 命令。这不会引入轻量版 loopx；它只是让 `plan`、`build`、`review` 能看到项目事实，同时保持完整闭环。
+
 `intake` 保存一次需求的 clarify 快照；`workflows` 保存当前任务的运行时工作副本；`changes` 保存本次需求对长期行为的 change delta；`specs` 只保存 archive 后的长期领域行为契约。
 
-`views/` 和 `workflows/<slug>/view/` 是 `loopx render` 生成的派生 HTML 阅读视图，只服务于人的浏览和评审，可以随时重新生成；agent 和工具仍应读取、修改 Markdown 与 JSON 产物。
+`views/` 和 `workflows/<slug>/view/` 是 plan 后写入、也可由 `loopx render` 重新生成的派生 HTML 阅读视图，只服务于人的浏览和评审；agent 和工具仍应读取、修改 Markdown 与 JSON 产物。
 
 ### 文档关注边界
 
@@ -364,11 +398,12 @@ loopx 在当前项目下写入 `.loopx/`：
 - `.loopx/workflows/<slug>/spec.md`：当前需求工作副本。
 - `.loopx/workflows/<slug>/plan.md`、`architecture.md`、`development-plan.md`、`test-plan.md`：当前任务的计划、架构和验证约定。
 - `.loopx/workflows/<slug>/execution-record.md`、`review-report.md`：执行证据和评审结论。
-- `.loopx/views/index.html` 与 `.loopx/workflows/<slug>/view/index.html`：由 `loopx render` 生成的阅读入口。
+- `.loopx/views/index.html` 与 `.loopx/workflows/<slug>/view/index.html`：plan 后写入、也可由 `loopx render` 重新生成的阅读入口。
 
 用户可以阅读和按流程修改的事实源文档：
 
 - `.loopx/workflows/<slug>/*.md`：当前 workflow 的可编辑工作副本；修改后仍需通过对应阶段门禁。
+- `.loopx/config.json`：workspace 配置、项目规则/spec 来源发现结果和默认验证命令；当仓库的 canonical 命令或规则文件变化时可以更新。
 - `.loopx/context/domain.md` 和 `.loopx/agents/*.md`：项目级背景、术语和 agent 协作约定。
 - `.loopx/changes/active/<change-id>/*.md`：plan 生成的 change proposal、design、tasks 和 spec delta；修改后应重新过 plan/build/review。
 - `.loopx/specs/<domain>/spec.md`：archive 后的长期行为规格；通常由 `archive` 同步，人工改动需要保持和后续 change delta 一致。
@@ -380,7 +415,7 @@ loopx 在当前项目下写入 `.loopx/`：
 - `.loopx/intake/clarify-*.md`：clarify 快照，用于审计和追溯；不要当作长期 specs 修改。
 - `.loopx/changes/active/<change-id>/slices.json`、`artifact-graph.json`：计划结构化数据，build/review/archive 会消费。
 - `.loopx/autopilot/<slug>/run.json`、`.loopx/build-active.json`：编排和 stop-hook 运行态。
-- `.loopx/views/` 和 `.loopx/workflows/<slug>/view/`：HTML 派生视图，可删除后用 `loopx render` 重新生成，不应作为事实源编辑。
+- `.loopx/views/` 和 `.loopx/workflows/<slug>/view/`：HTML 派生视图，plan 后自动写入，可删除后用 `loopx render` 重新生成，不应作为事实源编辑。
 
 ## 安装诊断与修复
 
@@ -402,6 +437,12 @@ loopx repair-install
 node scripts/install-skills.mjs --check
 ```
 
+检查 bundled skill 治理状态：
+
+```bash
+node scripts/verify-skills.mjs
+```
+
 ## Codex Workflow Hook
 
 `install-skills.mjs` 和 Codex plugin 安装脚本会自动把 `scripts/codex-workflow-hook.mjs` 安装到：
@@ -453,9 +494,17 @@ node scripts/codex-stop-hook.mjs
 npm test
 ```
 
+`npm test` 会先运行 bundled skill 治理检查，再运行 Node 测试套件：
+
+```bash
+node scripts/verify-skills.mjs
+node --test test/*.test.mjs
+```
+
 也可以直接执行项目内的验证命令：
 
 ```bash
+node scripts/verify-skills.mjs
 node --test test/*.test.mjs
 node scripts/install-skills.mjs --check
 node --test plugins/loopx/scripts/plugin-install.test.mjs
@@ -472,6 +521,7 @@ node src/cli.mjs status --json
 - `README.zh-CN.md`
 - `package.json`
 - `scripts/install-skills.mjs`
+- `scripts/verify-skills.mjs`
 - `scripts/codex-stop-hook.mjs`
 - `scripts/codex-workflow-hook.mjs`
 - `assets/logo.svg`
@@ -482,4 +532,4 @@ node src/cli.mjs status --json
 
 ## 版本
 
-当前 npm 包版本：`0.1.4`。
+当前 npm 包版本：`0.1.6`。

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ai-content-space/loopx",
   "type": "module",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "Skill-first loopx workflow product for Codex",
   "repository": {
     "type": "git",
@@ -22,6 +22,7 @@
     "README.zh-CN.md",
     "package.json",
     "scripts/install-skills.mjs",
+    "scripts/verify-skills.mjs",
     "scripts/codex-stop-hook.mjs",
     "scripts/codex-workflow-hook.mjs",
     "assets/logo.svg",
@@ -35,6 +36,6 @@
   },
   "scripts": {
     "postinstall": "node scripts/install-skills.mjs",
-    "test": "node --test test/*.test.mjs"
+    "test": "node scripts/verify-skills.mjs && node --test test/*.test.mjs"
   }
 }

package/plugins/loopx/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "loopx",
-  "version": "0.1.3",
+  "version": "0.1.6",
   "description": "Skill-first loopx workflow product for Codex",
   "skills": "./skills/",
   "interface": {

package/plugins/loopx/skills/archive/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: archive
-description: Sync an approved loopx change delta into long-lived specs after review is done.
+description: "Archives an approved loopx change delta into long-lived specs and writes an ADR candidate after done approval. Not for active builds or unapproved reviews."
+when_to_use: "archive, done workflow, spec delta, long-lived specs, ADR candidate, review approved, 归档, 同步规格"
+metadata:
+  version: "0.1.6"
 argument-hint: "<workflow slug>"
 ---
 
@@ -8,7 +11,7 @@ argument-hint: "<workflow slug>"
 
 ## Purpose
 
-Use `archive` after a loopx workflow has reached `done`. It syncs the accepted change delta into long-lived `.loopx/specs/` files, archives the change staging directory, and writes an advisory ADR candidate.
+Use `archive` after a loopx workflow has reached `done`, or immediately after an approved review that is waiting for `review -> done` completion. It syncs the accepted change delta into long-lived `.loopx/specs/` files, archives the change staging directory, and writes an advisory ADR candidate.
 
 The accepted delta is requirement-based, not a changelog block. Archive applies:
 
@@ -21,7 +24,7 @@ into the current long-lived `## Requirements` state for each target domain.
 
 ## Inputs
 
-- `<workflow slug>` for a completed loopx workflow
+- `<workflow slug>` for a completed loopx workflow, or for a review-approved workflow whose next route is `done`
 
 ## Behavior
 
@@ -31,9 +34,12 @@ Run:
 loopx archive <slug>
 ```
 
+If review already approved the workflow and the only pending transition is `review -> done`, this command consumes that completion transition before archiving. Do not ask the user to run a separate `loopx approve <slug> --from review --to done` command in that case.
+
 Then report in Chinese:
 
 - whether the change was archived
+- whether `review -> done` was consumed by archive
 - which long-lived spec files were updated
 - the archived change path
 - the ADR candidate path, if written
@@ -41,7 +47,7 @@ Then report in Chinese:
 
 ## Boundaries
 
-- Do not run archive before `review -> done` has been approved.
+- Do not run archive before review has approved the workflow and routed it to `done`.
 - Do not archive malformed requirement deltas. ADDED and MODIFIED entries must use `### Requirement:`, SHALL/MUST language, and at least one `#### Scenario:`.
 - Do not archive when `execution-record.md` declares non-empty `remaining_scope`, `completion_claim` other than `full`, or a mismatch between `planned_scope` and `implemented_scope`; route back to build/plan instead.
 - Do not edit implementation code.

package/plugins/loopx/skills/autopilot/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: autopilot
-description: Richer internal-phase loopx autonomous orchestration over the public clarify/plan/build/review flow.
+description: "Runs one bounded autonomous loopx orchestration over clarify, plan, build, and review while preserving canonical artifacts. Not for manual gate-by-gate control."
+when_to_use: "autopilot, autonomous loopx run, end-to-end workflow, run all stages, bounded orchestration, 自动执行, 全流程"
+metadata:
+  version: "0.1.6"
 argument-hint: "<workflow slug>"
 ---
 

package/plugins/loopx/skills/build/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: build
-description: Ralph-style loopx execution runtime under the public build stage.
+description: "Executes an approved loopx plan or review rework contract with evidence, verification, deslop, and regression gates. Not for unclear requirements or independent review."
+when_to_use: "build, implement approved plan, execute PRD, --from-review, review rework, implementation fixes, 执行, 实现, 修改"
+metadata:
+  version: "0.1.6"
 argument-hint: "[--no-deslop] <approved PRD path or workflow slug> | --from-review <review artifact path>"
 ---
 
@@ -30,6 +33,7 @@ By default, `build` is not a one-shot draft writer. It is a persistence loop wit
 - Execution may parallelize internally without exposing a public `team` stage.
 - `build` does not replace `review`.
 - `execution-record.md` remains the sole canonical execution and verification artifact.
+- `.loopx/config.json` is supporting context for existing project AI rules, existing spec sources, and discovered verification commands; use it to preserve local sources of truth, not to skip loopx stages.
 - Feature work and bug fixes should use `tdd`: write a failing test, confirm it fails for the intended reason, then implement the smallest passing change.
 - Bug, test-failure, build-failure, and unexpected-behavior work should use `debug` before proposing fixes.
 - Completion and review-ready claims should use `verify` before they are stated.
@@ -72,6 +76,8 @@ Compatible skill / CLI input:
 When invoked with a PRD path, derive `<slug>` from `prd-<slug>.md` and still use the matching workflow-local plan package and test spec.
 
 When invoked with `--from-review`, derive `<slug>` from the workflow directory, treat the review artifact as the implementation-fix contract, and load the matching PRD, test spec, previous `execution-record.md`, and workflow-local plan package as supporting context. This Codex skill invocation consumes the `review -> build` rework intent; users should not need a separate bash `loopx approve ... --from review --to build` step for the normal Codex-facing flow.
+
+Also load `.loopx/config.json` when present. Its `project_conventions` entries identify existing project rule/spec files that should be preserved, and its `verification_commands` entries are the first project-native commands to consider for fresh evidence.
 </Inputs>
 
 <Execution_Model>
@@ -194,6 +200,8 @@ These support artifacts are runtime aids only. They must not become new canonica
 <Final_Response_Contract>
 When `build` reaches review handoff readiness, the final response must include an explicit next skill command using the execution record path:
 
+Default review handoff after build readiness:
+
 ```text
 Next:
 $review .loopx/workflows/<slug>/execution-record.md

package/plugins/loopx/skills/clarify/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: clarify
-description: Comprehensive loopx clarify skill for requirements, boundaries, and design-ready specs.
+description: "Clarifies ambiguous loopx work into requirements, non-goals, decision boundaries, and design-ready specs before planning. Not for already-approved plans or concrete implementation tasks."
+when_to_use: "clarify, requirements, ambiguous request, unclear scope, non-goals, decision boundaries, acceptance criteria, 需求澄清, 范围不清"
+metadata:
+  version: "0.1.6"
 ---
 
 # loopx Clarify
@@ -305,8 +308,11 @@ After the clarify spec is ready:
 
 Preferred explicit handoff contract:
 
-- Recommended invocation: `$plan <slug>`
-- Artifact-pinned invocation when needed: `$plan --direct .loopx/intake/clarify-<slug>-<timestamp>.md`
+- Default handoff after normal loopx clarify: `$plan <slug>`
+- Conditional artifact-pinned handoff: `$plan --direct <spec-path>`
+- Recommend `$plan --direct <spec-path>` when the user explicitly wants to plan from a specific requirements artifact, when the source is external/manual/legacy, or when multiple plausible spec files exist and the user has chosen one as the planning source of truth.
+- Do not use `$plan --direct` to work around unclear workflow state, missing approvals, or an uncertain slug; inspect or repair the loopx runtime state instead.
+- For the normal loopx clarify happy path, prefer `$plan <slug>` because the active workflow slug already anchors the clarify artifact and runtime state.
 - Consumer behavior: treat the clarify spec as the source of truth for intent, non-goals, decision boundaries, constraints, and design direction; do not reopen clarification by default
 
 `clarify` itself does not implement the feature. The handoff recommendation must name `plan` as the next workflow step.

package/plugins/loopx/skills/debug/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: debug
-description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
+description: "Finds root cause for bugs, failing tests, build failures, regressions, and unexpected behavior before fixes. Not for new feature planning or routine code review."
+when_to_use: "debug, bug, test failure, build failure, regression, unexpected behavior, root cause, 报错, 失败, 回归, 排查"
+metadata:
+  version: "0.1.6"
 ---
 
 # Systematic Debugging

package/plugins/loopx/skills/go-style/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: go-style
-description: Go language style support for loopx. Use before creating or editing Go (.go) files, especially inside build execution lanes.
+description: "Applies loopx Go coding style for .go edits, tests, errors, context, naming, and interface boundaries. Not for non-Go code or Kratos-specific architecture by itself."
+when_to_use: "go-style, Go, golang, .go files, go tests, gofmt, idiomatic Go, Go style, Go 代码"
+metadata:
+  version: "0.1.6"
 ---
 
 # Go Style

package/plugins/loopx/skills/kratos/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: kratos
-description: Go-Kratos framework support for loopx. Use for Kratos microservices, proto/buf API work, service/biz/data layering, Kratos middleware, auth, configuration, and troubleshooting.
+description: "Supports Go-Kratos microservices, proto/buf APIs, service/biz/data layers, middleware, auth, config, and troubleshooting. Not for generic Go style alone."
+when_to_use: "kratos, Go-Kratos, proto, buf, service layer, biz layer, data layer, middleware, auth, config, Kratos 微服务"
+metadata:
+  version: "0.1.6"
 ---
 
 # Kratos

package/plugins/loopx/skills/plan/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: plan
-description: Consensus-first loopx planning skill with Planner, Architect, and Critic review.
+description: "Creates a consensus-first loopx plan package with Planner, Architect, and Critic review from an approved spec. Not for unresolved requirements or direct implementation."
+when_to_use: "plan, planning, consensus planning, PRD, architecture plan, test plan, approved clarify spec, 规划, 方案, 架构评审"
+metadata:
+  version: "0.1.6"
 argument-hint: "[--interactive] [--deliberate] [--direct <spec-path>] <clarified task or spec path>"
 ---
 
@@ -170,6 +173,14 @@ On approval, write canonical planning artifacts:
 - `.loopx/changes/active/<change-id>/slices.json`
 - `.loopx/changes/active/<change-id>/artifact-graph.json`
 
+Also generate derived HTML reading views:
+
+- `.loopx/workflows/<slug>/view/index.html`
+- `.loopx/workflows/<slug>/view/plan.html`
+- `.loopx/views/index.html`
+
+The HTML files are derived reading views for human plan review. They are not canonical fact sources; Markdown and JSON remain authoritative.
+
 The final plan must include:
 
 - ADR: Decision, Drivers, Alternatives considered, Why chosen, Consequences, Follow-ups
@@ -196,6 +207,24 @@ In `--interactive` mode, ask for the next lane:
 Without `--interactive`, report the approved plan and recommended next command, but do not launch execution.
 </Consensus_Workflow>
 
+<Final_Response_Contract>
+Default build handoff after an approved plan package:
+
+```text
+Next:
+$build .loopx/plans/prd-<slug>.md
+```
+
+Use the artifact-first PRD path because it pins build to the approved plan package. Do not emit `$build <slug>` as the primary handoff when `.loopx/plans/prd-<slug>.md` is known. If execution is not approved or plan gates remain blocked, state the blocker instead of emitting a build handoff.
+
+Also report the generated HTML reading entrypoint so the user can review the plan without running another command:
+
+```text
+HTML:
+.loopx/workflows/<slug>/view/index.html
+```
+</Final_Response_Contract>
+
 <Runtime_State_Machine>
 `plan` must keep the planning gate machine-checkable. Runtime state should track:
 
@@ -246,6 +275,7 @@ Primary outputs:
 - approved plan package under `.loopx/workflows/<slug>/`
 - canonical PRD and test spec under `.loopx/plans/`
 - change artifacts under `.loopx/changes/active/<change-id>/`
+- derived HTML reading views under `.loopx/workflows/<slug>/view/` and `.loopx/views/`
 - consensus review summary with Planner / Architect / Critic evidence
 - next-step recommendation
 

package/plugins/loopx/skills/review/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: review
-description: Repo-local acceptance surface for loopx.
+description: "Reviews a loopx build execution record for acceptance, code risks, evidence quality, and architecture smells. Not for doing implementation work or replanning."
+when_to_use: "review, code review, acceptance, go no-go, execution-record, architecture smell, build complete, 审查, 验收"
+metadata:
+  version: "0.1.6"
 argument-hint: "<execution-record path or workflow slug>"
 ---
 
@@ -22,6 +25,8 @@ Compatible skill / CLI input:
 
 When invoked with an execution record path, derive `<slug>` from the workflow directory and evaluate the matching active run.
 
+When present, use `.loopx/config.json` as supporting context for project-native verification commands, existing AI rule files, and existing spec sources. Do not treat those external or pre-existing sources as replacements for the loopx execution record and review artifact.
+
 ## Expected Outputs
 
 - a review artifact tied to the run being evaluated
@@ -42,6 +47,7 @@ Use stable machine values only where they are commands, file paths, JSON/state f
 - Use this only after build has produced execution and verification evidence for a specific run.
 - Stop here if review evidence is incomplete. `review` remains an independent gate and does not auto-complete the workflow.
 - Review must include code review of the build-owned implementation diff. Do not limit review to artifact/schema checks.
+- Review should compare verification evidence against project-native commands recorded in `.loopx/config.json` when available, while still accepting stronger task-specific verification from the approved plan.
 - Review must include the architecture-smell lane as part of review evidence. This is not a new workflow stage and must not create extra user steps.
 - Review must compare the execution scope against the approved workflow scope. If `execution-record.md` declares non-empty `remaining_scope`, `completion_claim` other than `full`, or a mismatch between `planned_scope` and `implemented_scope`, review must return no-go and route to build or plan. A partial slice may be accepted as useful work, but it must not be approved as full workflow completion.
 - Code review findings should focus on real bugs, regressions, missing tests, broken contracts, security/data-integrity risks, and user-visible behavior gaps.
@@ -59,6 +65,8 @@ Every no-go review result must end with a concrete next command block.
 
 For implementation fixes:
 
+Default implementation-fix handoff:
+
 ```text
 Next:
 $build --from-review .loopx/workflows/<slug>/review-report.md

package/plugins/loopx/skills/tdd/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: tdd
-description: Use when implementing any feature or bugfix, before writing implementation code
+description: "Guides feature and bugfix implementation through a failing test before production code and red-green-refactor discipline. Not for generated files or throwaway prototypes."
+when_to_use: "tdd, failing test first, feature implementation, bugfix, regression test, red green refactor, 测试先行"
+metadata:
+  version: "0.1.6"
 ---
 
 # Test-Driven Development (TDD)

package/plugins/loopx/skills/verify/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: verify
-description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+description: "Requires fresh verification evidence before claiming work is complete, fixed, passing, review-ready, or ready to commit. Not for speculative confidence or stale results."
+when_to_use: "verify, completion claim, fixed claim, tests pass, review-ready, commit, fresh evidence, 验证, 完成前检查"
+metadata:
+  version: "0.1.6"
 ---
 
 # Verification Before Completion