@jspg-ai/coding-bb 0.0.3-beta.9 → 0.0.5-beta.1

package/cbb/worktrees/skills/cbb-worktree-push/scripts/push-worktrees.js

@@ -7,7 +7,9 @@ require('./silence-popup');
  *   node push-worktrees.js <wt_path>          # wt_path 必须是 <ws_root>/.worktrees/worktree-<branch> 形态
  *
  * 行为：
- *   1. 扫描 <ws_root>/.worktrees/worktree-<branch>/ 下所有 git 仓库（workspace + 各 app 子 worktree）
+ *   1. 按需求名发现参与仓库（ADR 0002 双布局）：
+ *      - worktree 布局：.worktrees/worktree-<branch>/ 的 workspace + 其 .codespace/<app>/ 容器内各 app worktree（镜像主布局，ADR 0003）
+ *      - 本地布局：根 / .codespace/<app>/ 检出恰在 <branch> 分支上
  *   2. 对每个仓库调 push-core.pushSingle（已建立 upstream 时直接 push -u；否则建立 upstream）
  *   3. 逐个报告状态，输出末行 PUSH_RESULT
  *
@@ -28,6 +30,7 @@ require('./silence-popup');
 const { pushSingle } = require('./push-core');
 const fs = require('fs');
 const path = require('path');
+const { execSync } = require('child_process');
 
 function resolveInputs(argv) {
   // argv[2] 单独：wt_path 形式
@@ -56,35 +59,79 @@ function isGitRepo(p) {
   }
 }
 
+/** 读取 CBB-WORKSPACE.json 的 app 名列表（旧布局兼容判定用；缺失返回 []） */
+function loadAppNames(wsRoot) {
+  try {
+    const cfg = JSON.parse(fs.readFileSync(path.join(wsRoot, 'CBB-WORKSPACE.json'), 'utf-8'));
+    return Array.isArray(cfg.apps) ? cfg.apps.map(a => a.name).filter(Boolean) : [];
+  } catch (e) {
+    return [];
+  }
+}
+
+function currentBranch(p) {
+  try {
+    return execSync('git branch --show-current', { cwd: p, encoding: 'utf-8', stdio: ['ignore', 'pipe', 'pipe'] }).toString().trim();
+  } catch (e) { return ''; }
+}
+
 /**
- * 扫描 worktree 下的所有 git 仓库
- * - workspace worktree：<ws_root>/.worktrees/worktree-<branch>/ 本身
- * - app worktree：<ws_root>/.worktrees/worktree-<branch>/<app_name>/（嵌套子目录）
+ * 按需求名发现参与仓库（ADR 0002 双布局）：
+ *   布局一 worktree：.worktrees/worktree-<branch>/ 的 workspace + 其 .codespace/<app>/ 容器内 app worktree（ADR 0003 镜像主布局；≤beta.23 旧平铺顶层布局按配置 app 名兼容）
+ *   布局二 本地模式：根 / .codespace/<app>/ 的检出恰在 <branch> 分支上（同名仓库以 worktree 布局优先）
+ * 两者皆空 → error。
  */
 function scanWorktreeRepos(wsRoot, branch) {
   const wtRoot = path.join(wsRoot, '.worktrees', 'worktree-' + branch);
   const repos = [];
 
-  if (!fs.existsSync(wtRoot)) {
-    return { wtRoot, repos, error: 'worktree 目录不存在：' + wtRoot };
+  // 布局一：worktree
+  if (fs.existsSync(wtRoot)) {
+    if (isGitRepo(wtRoot)) {
+      repos.push({ name: 'workspace', wt: wtRoot, repo: wsRoot, layout: 'worktree' });
+    }
+    // app worktree 收拢在 .codespace/ 容器内（镜像主布局，ADR 0003）
+    const appContainer = path.join(wtRoot, '.codespace');
+    if (fs.existsSync(appContainer)) {
+      for (const e of fs.readdirSync(appContainer, { withFileTypes: true })) {
+        if (!e.isDirectory()) continue;
+        const appWt = path.join(appContainer, e.name);
+        if (!isGitRepo(appWt)) continue;
+        repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.codespace', e.name), layout: 'worktree' });
+      }
+    }
+    // 兼容 ≤beta.23 旧平铺布局：按配置 app 名精确匹配（避免把根仓库自带的嵌套 git 目录误判为 app）
+    for (const name of loadAppNames(wsRoot)) {
+      if (repos.some(r => r.name === name)) continue;
+      const legacyWt = path.join(wtRoot, name);
+      if (fs.existsSync(path.join(legacyWt, '.git'))) {
+        console.error('⚠️  ' + name + ' 仍是旧平铺布局（' + legacyWt + '），建议重跑 cbb-worktree-init 迁移到 .codespace/ 容器');
+        repos.push({ name, wt: legacyWt, repo: path.join(wsRoot, '.codespace', name), layout: 'worktree' });
+      }
+    }
   }
 
-  // workspace worktree（自身是 git worktree）
-  if (isGitRepo(wtRoot)) {
-    repos.push({ name: 'workspace', wt: wtRoot, repo: wsRoot });
+  // 布局二：本地模式（检出在需求分支上）
+  const names = new Set(repos.map(r => r.name));
+  if (!names.has('workspace') && isGitRepo(wsRoot) && currentBranch(wsRoot) === branch) {
+    repos.push({ name: 'workspace', wt: wsRoot, repo: wsRoot, layout: 'local' });
   }
-
-  // app worktree（嵌套子目录）
-  const entries = fs.readdirSync(wtRoot, { withFileTypes: true });
-  for (const e of entries) {
-    if (!e.isDirectory()) continue;
-    // 跳过 . 开头的隐藏目录（如 .va、.claude、.qoder）
-    if (e.name.startsWith('.')) continue;
-    const appWt = path.join(wtRoot, e.name);
-    if (!isGitRepo(appWt)) continue;
-    repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.codespace', e.name) });
+  const codeDir = path.join(wsRoot, '.codespace');
+  if (fs.existsSync(codeDir)) {
+    for (const name of fs.readdirSync(codeDir).sort()) {
+      if (names.has(name)) continue;
+      const appDir = path.join(codeDir, name);
+      if (!isGitRepo(appDir)) continue;
+      if (currentBranch(appDir) === branch) {
+        repos.push({ name, wt: appDir, repo: appDir, layout: 'local' });
+      }
+    }
   }
-  return { wtRoot, repos, error: null };
+
+  const error = repos.length === 0
+    ? ('未发现需求 ' + branch + ' 的参与仓库（worktree 不存在，且无仓库检出在 ' + branch + ' 分支上）')
+    : null;
+  return { wtRoot, repos, error };
 }
 
 /**

package/cbb/worktrees/skills/cbb-worktree-push/scripts/silence-popup.js

@@ -4,7 +4,7 @@
 // koffi is resolved from cbb global install (no local node_modules needed).
 //
 // 唯一真源：cbb/worktrees/_shared/scripts/silence-popup.js
-// 由 scripts/sync-shared.js 展开到各 skill 的 scripts/ 下（init / extend / close / push）。
+// 由 scripts/sync-shared.js 展开到各 skill 的 scripts/ 下（init / close / push / local-mode）。
 // skill 内同目录引用：脚本第一行 `require('./silence-popup')`。
 if (process.platform === 'win32') {
   try {

package/config/{workspace-config.sample.json → CBB-WORKSPACE.sample.json}

@@ -1,5 +1,5 @@
 {
-    "_comment": "AI 开发工作空间配置样例（请勿修改本文件，复制为工作空间根目录的 workspace-config.json 后编辑使用）。apps 数组中每个对象需包含：name（应用名，同时作为 .codespace/ 子目录名）、repo（Git 仓库地址，支持 SSH 或 HTTPS）、side（仓库类型，'front' 表示前端工程，'back' 表示后端工程，'mixed' 表示前后端混合工程）；可选 desc（该应用的职责描述，便于人与 AI 理解应用分工）。",
+    "_comment": "AI 开发工作空间配置样例（请勿修改本文件，复制为工作空间根目录的 CBB-WORKSPACE.json 后编辑使用）。apps 数组中每个对象需包含：name（应用名，同时作为 .codespace/ 子目录名）、repo（Git 仓库地址，支持 SSH 或 HTTPS）、side（仓库类型，'front' 表示前端工程，'back' 表示后端工程，'mixed' 表示前后端混合工程）；可选 desc（该应用的职责描述，便于人与 AI 理解应用分工）。",
     "apps":
     [
         {

package/config/openspec/schemas/spec-driven/schema.yaml

@@ -224,6 +224,14 @@ apply:
 
     `plan.md` 跟 change 同住一个目录，archive 阶段会被一起带走。
 
+    **收尾（全部任务翻成 `- [x]` 后执行；本段为项目级硬约束，覆盖官方 apply 模板自带的完成提示语）：**
+
+    1. **未决项自检**（逐项确认，任何一项未过都不得宣布完成）：
+       - change 产物（proposal.md / design.md / specs/** / tasks.md / plan.md）已提交到需求分支（轻量模式：空间根 main 分支）；未提交时先询问用户是否现在提交（可随 cbb-worktree-push 一并推送；轻量模式提交后即 push）
+       - 本会话产生的临时文件与环境改动（备份目录、未回写远端的本地提交、cherry-pick 等）已列清并交用户决策
+    2. **输出顺序纪律**：存在未决项时，本轮只列未决项并等待用户决策；**禁止同轮输出"下一步建议"**，禁止出现"规划与实施均已完成""可运行 archive"之类表述（产物未提交时归档会丢规划产物）
+    3. **全部未决项关闭后，唯一可建议的下一步是 `/opsx:verify`**：本项目工作流为 propose → apply → verify → archive，verify（强制 code-review + 产出 cr.md）是 archive 的前置阶段；**禁止直接建议 archive**，官方模板的 "You can archive this change" 提示语以本段为准
+
 verify:
   tracks: cr.md
   requires: [tasks]
@@ -236,3 +244,15 @@ verify:
        即便 AI 自认能 review,仍必须调 skill。
     2. **MANDATORY 产出 `cr.md`**:把完整 Verification Report 写到 `openspec/changes/<name>/cr.md`,
        缺则视为 verify 未完成。报告必须包含五段:Summary / CRITICAL / WARNING / SUGGESTION / Code Review。
+
+    **收尾（cr.md 产出且无 CRITICAL 遗留后执行；本段为项目级硬约束，覆盖官方 verify 模板自带的完成提示语）：**
+
+    verify 通过后，用 AskUserQuestion（固定选项）向用户提供两条路径并等待选择，禁止替用户决定、禁止单一路径直接建议归档：
+
+    - **路径 A · 先验收后归档（推荐）**：执行 `cbb-worktree-push` 推送 feature 分支并提 MR 到测试分支 → 测试环境部署、用户验收 → 验收要改则在 worktree 内修复后再次 push（小改动无需重跑 verify）→ 验收通过后才 `/opsx:archive`
+    - **路径 B · 先归档后推送**：立即 `/opsx:archive` 落定变更产物（归档移动与 spec 同步发生在 feature 分支上）→ 再执行 `cbb-worktree-push` 一并推送 → 提 MR 到测试分支验收。注意：验收若发现问题，产物已归档，修复需走新 change 或将归档移回后继续；适合改动小、验收把握大的场景
+    - **Step 7 交付选择（ADR 0008）**：两条路径的 `cbb-worktree-push` 推送完成后，除「提 MR」外均可选「直接合并」——合测试分支不要求归档，合主干要求已归档 + 强提醒确认；合并成功不删分支（删除归 `cbb-worktree-close` 收尾门禁）
+
+    用户选定后按该路径执行；官方模板的单一 "suggest archive" 提示语以本段为准。
+
+    **轻量模式变体**（本次 change 完全不涉及应用代码，产物在空间根仓库）：无 worktree push / 测试分支 MR 环节，两条路径替换为——A（推荐）"先 push main 交付、观察无回归后再 archive" / B"立即 archive 落定产物，再 push main"；main 提交不得悬空本地。

package/config/upstream-mirrors.json

@@ -8,5 +8,10 @@
   "openspec": [
     "https://registry.npmmirror.com",
     "https://registry.npmjs.org"
+  ],
+  "external": [
+    "https://gh-proxy.com/",
+    "https://ghfast.top/",
+    ""
   ]
 }

package/external/frontend-design/.version

@@ -0,0 +1,6 @@
+{
+  "repo": "anthropics/skills",
+  "ref": "41bbe19d1a1a7eaab5e7bb9050a417e5c6cffc8f",
+  "path": "skills/frontend-design",
+  "updatedAt": "2026-09-28T07:10:02.694Z"
+}

package/external/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/external/frontend-design/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: frontend-design
+description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
+license: Complete terms in LICENSE.txt
+---
+
+# Frontend Design
+
+Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.
+
+## Ground your designs in the subject matter
+
+If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.
+
+## Design principles
+
+For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.
+
+Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.
+
+Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.
+
+Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.
+
+Avoid these default typographic treatments; they are the commonest tells of a generated page:
+- Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
+- Using all caps for labels.
+- Adding unnecessary typographic labels above content.
+
+Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.
+
+Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.
+
+Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
+
+## Process: plan, review against the brief, build, critique
+
+For calibration, AI-generated design right now clusters around some traits:
+1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
+2. a near-black background with a single bright acid-green or vermilion accent;
+3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
+4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
+5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.
+
+All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+
+Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.
+- Color: describe the core base palette as 4–6 named hex values.
+- Type: the typefaces and their roles.
+- Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
+- Principles: the high-level guidance for what makes this page unique.
+
+Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.
+
+When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.
+
+## Restraint and self-critique
+
+Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
+
+## More on writing in design
+
+Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
+
+Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.
+
+Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
+
+Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
+
+Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

package/openspec/.version

@@ -1,5 +1,5 @@
 {
-  "version": "1.13.1",
+  "version": "1.13.2",
   "repo": "Fission-AI/OpenSpec",
-  "renderedAt": "2026-09-19T13:22:53.815Z"
+  "renderedAt": "2026-09-28T07:29:28.008Z"
 }

package/openspec/commands/archive.md

@@ -80,20 +80,27 @@ In both branches, never create the root as a side effect: do not run `openspec i
 
 3. **Check task completion status**
 
-   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
-
-   A checkbox is complete when its only content is `x` or `X`; spacing inside
-   the brackets does not matter, so `- [ x]` counts as complete too. Every
-   other marker is incomplete - `- [ ]`, an empty `- []`, and markers OpenSpec
-   assigns no meaning to such as `- [~]` or `- [-]`. Never read an unfamiliar
-   marker as complete.
+   Run `openspec list --json` with the same selected-root flags and find the
+   entry in `changes` whose `name` exactly matches the selected change.
+   Require exactly one match and nonnegative integer `totalTasks` and
+   `completedTasks`, with `completedTasks <= totalTasks`. The CLI resolves
+   the schema's tracked task files, including custom artifact names, output
+   paths, and globs.
+   Incomplete tasks = `totalTasks - completedTasks`.
+
+   Do not infer task completion from artifact status or the absence of a
+   top-level `tasks.md`. If the lookup fails, returns invalid JSON, omits or
+   duplicates the selected change, or returns invalid counts, report the problem
+   and stop before syncing or archiving.
+   The CLI counts only `x`/`X` checkbox markers as complete;
+   other markers, including unfamiliar ones, remain incomplete.
 
    **If incomplete tasks found:**
    - Display warning showing count of incomplete tasks
    - Prompt user for confirmation to continue
    - Proceed if user confirms
 
-   **If no tasks file exists:** Proceed without task-related warning.
+   **If `totalTasks` is zero:** Proceed without a task-related warning.
 
 4. **Assess delta spec sync state**
 

package/openspec/commands/bulk-archive.md

@@ -36,7 +36,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
 2. **Prompt for change selection**
 
    Ask the user to choose changes (multi-select):
-   - Show each change with its schema
+   - Show each change name and task status from the list output
    - Include an option for "All changes"
    - Allow any number of selections (1+ works, 2+ is the typical use case)
 
@@ -69,17 +69,24 @@ In both branches, never create the root as a side effect: do not run `openspec i
 
 3. **Batch validation - gather status for all selected changes**
 
+   Run `openspec list --json` once with the same selected-root flags for task
+   progress. If the lookup fails, returns invalid JSON, or omits any selected
+   change, contains a duplicate selected change, or returns invalid counts,
+   report the problem and stop before syncing or archiving the batch.
+
    For each selected change, collect:
 
    a. **Artifact status** - Run `openspec status --change "<name>" --json`
       - Parse `schemaName`, `artifacts`, `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`
       - Note which artifacts are `done` vs other states
 
-   b. **Task completion** - Read `artifactPaths.tasks.existingOutputPaths` from status JSON
-      - Complete means the checkbox holds only `x`/`X`, ignoring spacing
-        (`- [ x]` is complete); every other marker is incomplete (`- [ ]`,
-        `- []`, and unfamiliar ones such as `- [~]` or `- [-]`)
-      - If no tasks file exists, note as "No tasks"
+   b. **Task completion** - Find the `changes` entry from the list response whose `name` exactly matches this change
+      - Require nonnegative integer `totalTasks` and `completedTasks`, with `completedTasks <= totalTasks`
+      - Incomplete tasks = `totalTasks - completedTasks`
+      - The CLI resolves the schema's tracked task files, including custom artifact names, output paths, and globs
+      - Do not infer task completion from artifact status, an artifact id of `tasks`, or the absence of a top-level `tasks.md`
+      - The CLI counts only `x`/`X` checkbox markers as complete; other markers remain incomplete
+      - If `totalTasks` is zero, note as "No tasks"
 
    c. **Delta specs** - Check `artifactPaths.specs.existingOutputPaths` from status JSON
       - List which capability specs exist

package/openspec/commands/continue.md

@@ -32,7 +32,6 @@ In both branches, never create the root as a side effect: do not run `openspec i
 
    When prompting, present the top 3-4 most recently modified changes as options, showing:
    - Change name
-   - Schema (from `schema` field if present, otherwise "spec-driven")
    - Status (e.g., "0/5 tasks", "complete", "no tasks")
    - How recently it was modified (from `lastModified` field)
 

package/openspec/commands/explore.md

@@ -130,7 +130,7 @@ openspec list --json
 
 This tells you:
 - If there are active changes
-- Their names, schemas, and status
+- Their names and task status
 - What the user might be working on
 
 That is the *change* list - work in flight. It does not include the project's durable capabilities, so list those too:

package/openspec/commands/ff.md

@@ -86,7 +86,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
       - Dependencies are enablers, not gates: if a required artifact is still `blocked` only because you skipped a conditional dependency, write it anyway
       - Stop when every artifact in the required set is `done`, `skipped`, or was deliberately skipped
 
-   c. **If an artifact requires user input** (unclear context):
+   c. **If an artifact requires user input** (critically unclear context):
       - Ask the user to clarify
       - Then continue with creation
 

package/openspec/commands/onboard.md

@@ -373,7 +373,7 @@ Save to the `resolvedOutputPath` from `openspec instructions design --change "<n
 
 Finally, we break the work into implementation tasks—checkboxes that drive the apply phase.
 
-These should be small, clear, and in logical order.
+These should be small, clear, and in logical order. Each group carries the tests and documentation for its own work - the last group is only for integration checks.
 ```
 
 **DO:** Generate tasks based on specs and design:
@@ -396,12 +396,17 @@ Here are the implementation tasks:
 
 ---
 
-Each checkbox becomes a unit of work in the apply phase. Ready to implement?
+Each checkbox becomes a unit of work in the apply phase. Does this task breakdown look right?
 ```
 
-**PAUSE** - Wait for user to confirm they're ready to implement.
+**PAUSE** - Wait for user approval/feedback.
+
+After approval, save to the `resolvedOutputPath` from `openspec instructions tasks --change "<name>" --json`.
+
+Then ask:
+> "Tasks are saved. Ready to implement?"
 
-Save to the `resolvedOutputPath` from `openspec instructions tasks --change "<name>" --json`.
+**PAUSE** - Wait for user to confirm before implementation.
 
 ---