universal-dev-standards 6.14.1-beta.2 → 6.15.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (63) hide show
  1. package/bin/uds.js +2 -2
  2. package/bundled/ai/standards/developer-memory.ai.yaml +2 -2
  3. package/bundled/ai/standards/full-coverage-testing.ai.yaml +6 -4
  4. package/bundled/ai/standards/project-context-memory.ai.yaml +2 -2
  5. package/bundled/core/developer-memory.md +1 -1
  6. package/bundled/core/full-coverage-testing.md +4 -2
  7. package/bundled/core/open-work-tracking.md +13 -0
  8. package/bundled/core/project-context-memory.md +1 -1
  9. package/bundled/locales/COVERAGE.md +5 -4
  10. package/bundled/locales/zh-CN/CHANGELOG.md +53 -4
  11. package/bundled/locales/zh-CN/README.md +2 -2
  12. package/bundled/locales/zh-CN/SECURITY.md +3 -3
  13. package/bundled/locales/zh-CN/core/full-coverage-testing.md +5 -3
  14. package/bundled/locales/zh-CN/docs/AVAILABLE-STANDARDS.md +4 -4
  15. package/bundled/locales/zh-CN/docs/CHEATSHEET.md +1 -0
  16. package/bundled/locales/zh-CN/docs/CLI-INIT-OPTIONS.md +8 -3
  17. package/bundled/locales/zh-CN/docs/FEATURE-REFERENCE.md +5 -4
  18. package/bundled/locales/zh-CN/skills/README.md +2 -1
  19. package/bundled/locales/zh-CN/skills/commands/sdd-retro.md +1 -1
  20. package/bundled/locales/zh-CN/skills/dev-workflow-guide/SKILL.md +7 -7
  21. package/bundled/locales/zh-CN/skills/open-work-assistant/SKILL.md +133 -0
  22. package/bundled/locales/zh-TW/CHANGELOG.md +53 -4
  23. package/bundled/locales/zh-TW/README.md +2 -2
  24. package/bundled/locales/zh-TW/SECURITY.md +3 -3
  25. package/bundled/locales/zh-TW/core/developer-memory.md +3 -3
  26. package/bundled/locales/zh-TW/core/full-coverage-testing.md +5 -3
  27. package/bundled/locales/zh-TW/core/open-work-tracking.md +13 -2
  28. package/bundled/locales/zh-TW/core/project-context-memory.md +3 -3
  29. package/bundled/locales/zh-TW/docs/AVAILABLE-STANDARDS.md +4 -4
  30. package/bundled/locales/zh-TW/docs/CHEATSHEET.md +1 -0
  31. package/bundled/locales/zh-TW/docs/CLI-INIT-OPTIONS.md +8 -3
  32. package/bundled/locales/zh-TW/docs/FEATURE-REFERENCE.md +5 -4
  33. package/bundled/locales/zh-TW/skills/README.md +2 -1
  34. package/bundled/locales/zh-TW/skills/dev-workflow-guide/SKILL.md +7 -7
  35. package/bundled/locales/zh-TW/skills/open-work-assistant/SKILL.md +133 -0
  36. package/bundled/skills/.claude-plugin/plugin.json +1 -1
  37. package/bundled/skills/README.md +2 -1
  38. package/bundled/skills/dev-workflow-guide/SKILL.md +4 -4
  39. package/bundled/skills/open-work-assistant/SKILL.md +127 -0
  40. package/bundled/templates/gates/check-anti-fake-tests.mjs +183 -23
  41. package/bundled/templates/gates/check-stubs.mjs +85 -16
  42. package/package.json +2 -2
  43. package/src/commands/audit.js +4 -1
  44. package/src/commands/check.js +55 -6
  45. package/src/commands/config.js +2 -3
  46. package/src/commands/init.js +10 -3
  47. package/src/commands/update.js +239 -43
  48. package/src/i18n/messages.js +87 -0
  49. package/src/installers/hooks-installer.js +32 -5
  50. package/src/installers/skills-installer.js +45 -0
  51. package/src/reconciler/backup-locations.js +3 -2
  52. package/src/reconciler/backup-manager.js +14 -11
  53. package/src/reconciler/plan-executor.js +51 -7
  54. package/src/utils/copier.js +13 -8
  55. package/src/utils/flush-and-exit.js +37 -0
  56. package/src/utils/group-errors.js +65 -0
  57. package/src/utils/integration-generator.js +14 -5
  58. package/src/utils/skill-hash-ownership.js +33 -0
  59. package/src/utils/skill-link-rewriter.js +184 -0
  60. package/src/utils/skills-installer.js +115 -11
  61. package/src/utils/transient-fs.js +168 -14
  62. package/standards-registry.json +10 -19
  63. package/bundled/ai/standards/open-work-tracking.ai.yaml +0 -466
@@ -0,0 +1,133 @@
1
+ ---
2
+ name: open-work
3
+ source: ../../../../skills/open-work-assistant/SKILL.md
4
+ source_version: 1.0.0
5
+ translation_version: 1.0.0
6
+ last_synced: 2026-10-30
7
+ source_hash: 01f94f0311a4
8
+ status: current
9
+ scope: universal
10
+ description: |
11
+ [UDS] 選用的小幫手,幫忙追蹤跨工作階段仍未完成的工作:便宜的收件點、每個等待都有解除條件、下一步點名真實的東西。
12
+ Use when: 工作在工作階段之間漏掉、某個項目「等待中」好幾天卻沒人知道在等什麼、「下一步」只寫「繼續」。
13
+ Not for: 已經用議題追蹤器或看板管理工作而且沒有漏掉東西的專案;規劃功能——請用 /plan 或 /sdd。
14
+ Keywords: open work, backlog, inbox, waiting, release condition, next action, 開放工作, 待辦追蹤, 收件匣, 等待中, 解除條件.
15
+ allowed-tools: Read, Glob, Grep, Write, Bash
16
+ argument-hint: "[capture | waiting | next-action | report | 收件 | 等待 | 下一步 | 報告]"
17
+ ---
18
+
19
+ # 開放工作追蹤
20
+
21
+ > **語言**: [English](../../../../skills/open-work-assistant/SKILL.md) | 繁體中文 | [简体中文](../../../zh-CN/skills/open-work-assistant/SKILL.md)
22
+
23
+ **版本**: 1.0.0 | **最後更新**: 2026-10-30 | **適用**: Claude Code Skills
24
+
25
+ 幫忙避免工作在工作階段之間漏掉。想用才用。UDS 沒有任何東西要求你用。
26
+
27
+ ## 目的
28
+
29
+ 這個技能以前是一條標準,叫 `open-work-tracking`。UDS 把它搬到這裡,是因為那條標準只在一個專案上試過,而那個專案自己的使用沒有證實它。技能比較合適:工作開始漏掉時你拿起它,沒有漏掉時你放下它。
30
+
31
+ 舊標準的全文保留成參考文件:[open-work-tracking](../../core/open-work-tracking.md)。UDS 不再安裝它。本技能放的是其中值得保留的部分。
32
+
33
+ ## 什麼時候用、什麼時候不用
34
+
35
+ 先找出真正的問題是哪一個。去問使用者。不要為了一個沒有人遇到的問題去開一份追蹤清單。
36
+
37
+ | 出了什麼問題 | 什麼有幫助 |
38
+ |---|---|
39
+ | 做事做到一半冒出新想法,沒有便宜的地方可以放 | 一個只要兩個欄位的收件點 |
40
+ | 某個項目暫停「等待中」,之後沒人知道在等什麼 | 在等待旁邊寫下解除條件 |
41
+ | 已規劃的項目沒動工,時間過去,沒有東西指回它 | 一個日期,或定期看一眼清單 |
42
+
43
+ 三個都不是真的,就停下來並說明。專案已經有議題追蹤器或專案看板、而且在那裡沒有漏掉東西,就繼續用它。沒有人讀的第二份清單,只是多一個漏掉工作的地方。
44
+
45
+ ## 工作流程
46
+
47
+ ### 1. 收件:兩個欄位
48
+
49
+ 寫下日期和一句話。不要多寫。
50
+
51
+ | 日期 | 內容 |
52
+ |---|---|
53
+ | 2026-10-30 | 確認結構調整之後匯出作業還有沒有在跑 |
54
+
55
+ 這一步不要問分類、優先級或負責人。那些等整理清單時再決定。必填欄位多一個,大家就不再用這份清單。
56
+
57
+ ### 2. 等待:寫下什麼會解除它
58
+
59
+ 每個標為「等待中」的項目要有兩樣東西:在等什麼,以及什麼事件結束這個等待。優先選機器看得到的事件:日期、會出現的檔案、標籤、識別字。
60
+
61
+ | 項目 | status | asked-at | waiting for | release |
62
+ |---|---|---|---|---|
63
+ | 廠商報價 | asked-awaiting | 2026-10-27 | 廠商的回覆 | 檔案 `quotes/vendor-a.md` 存在 |
64
+
65
+ 寫明是哪一種等待:
66
+
67
+ - `not-yet-asked`:請求已經擬好或決定好,還沒有人送出。點名那份草稿或那個指令,送出它就解除這個等待。
68
+ - `asked-awaiting`:已經送出,還沒有回音。寫 `asked-at`(含年份的完整日期)。有年齡的項目可以在門檻到了時重新浮現,沒有年齡的不行。
69
+
70
+ 等待的是另一個專案裡的東西,就寫成 `<專案>:<物件>`,例如 `uds:v6.15.0` 或 `vibeops:docs/handoff.md`。專案是邏輯名稱,絕不是某一台機器上的目錄。
71
+
72
+ ### 3. 下一步:要點名東西
73
+
74
+ 下一步至少點名一個讀的人找得到的東西:檔案路徑、測試名稱、指令,或需求識別字。「繼續」和「處理剩下的」什麼都沒點名。
75
+
76
+ | 弱 | 較好 |
77
+ |---|---|
78
+ | 繼續做遷移 | 執行 `npm run migrate -- --dry-run`,並讀 `migrations/0042.sql` |
79
+
80
+ 已經問過、在等回覆的項目,可以把那個回覆當作下一步。這時它需要 `asked-at`、在等什麼、什麼解除它。
81
+
82
+ ### 4. 整理清單:三個出口
83
+
84
+ 挑一個固定的日子整理收件的項目。每個項目去三個地方之一:
85
+
86
+ 1. 變成規格或被追蹤的項目。
87
+ 2. 進入要做的工作清單。
88
+ 3. 丟掉,並寫一句為什麼。
89
+
90
+ 停在未整理狀態超過大約兩週的項目,要在報告裡被點名。沒有理由的丟棄,看起來和被誤刪的項目一模一樣。
91
+
92
+ ### 5. 報告:說出你看不到的部分
93
+
94
+ 報告「還有 N 項未完成」時,也要說你看了幾個來源、有幾個看不到。看不到的來源不是零。沒有這句話的報告,讀起來像是完整的。
95
+
96
+ 在回合結束、控制權交回給人的時候印出報告。報告絕不能擋住回合。「還有工作沒做完」幾乎永遠為真,而一個永遠紅燈的檢查會被關掉。
97
+
98
+ ### 6. 你看不到的事實
99
+
100
+ 有些事實,助理沒有任何來源可以讀:訊息有沒有寄出、對方有沒有回覆、有沒有核准。要手寫它們,必須附三樣東西:誰看到的(`observed-by`)、何時(`observed-at`,含年份),以及值是 `yes`、`no` 或 `unknown`。`unknown` 是正式的值,單獨計數,永遠不算完成。每筆觀察都顯示年齡。戳記只說有人看過一次,不說現在仍然如此。
101
+
102
+ 版本控制、規格標記或 CI 結果已經說明的事,不要手寫。
103
+
104
+ ### 7. 選用:執行參考檢查
105
+
106
+ UDS 在 CLI 裡附了這些規則的參考檢查程式:
107
+
108
+ ```bash
109
+ uds open-work next-action [files...] # 每個下一步都有點名東西嗎?
110
+ uds open-work waiting [files...] # 每個等待都有解除條件嗎?
111
+ uds open-work observations [files...] # 手寫的事實都有戳記嗎?
112
+ uds open-work self-test # 檢查程式自己遇到壞樣本還是會失敗嗎?
113
+ ```
114
+
115
+ 檢查程式靠欄位名稱找欄位,例如 `status`、`asked-at`、`waiting for`、`release`(上面的表格用的就是這些)。你的表格用別的詞,就在 `uds.project.yaml` 的 `open_work` 底下宣告。
116
+
117
+ 結束碼 0 表示沒有違反,1 表示有違反,2 表示檢查程式判定不了。2 不是通過。乾淨的結果只涵蓋它認得的詞。詞彙是第一版的猜測,沒有在真實使用上調整過。
118
+
119
+ ## 放在哪裡
120
+
121
+ 放在你的專案本來就會看的地方:議題追蹤器、專案看板、repo 裡的一個檔案。UDS 不替你選。兩個性質重要:那個地方受版本控制、或至少每個需要它的工作階段都讀得到,而且不是只放在某一個人私有的助理記憶裡。等待另一個專案的工作,要記在兩個專案的工作階段都讀得到的地方。
122
+
123
+ ## 本技能不宣稱的事
124
+
125
+ - 上面的規則來自一個專案。UDS 沒有證據顯示它們對其他專案有效。
126
+ - 門檻(兩個欄位、兩週、觀察七天算舊)是第一版的判斷,不是量測。
127
+ - 檢查程式讀的是表格和清單的結構。它分辨不出一則記錄是不是真的。
128
+
129
+ ## 相關
130
+
131
+ - [open-work-tracking](../../core/open-work-tracking.md):以前的標準,現在只供參考。它的要求編號是 OWT-001 到 OWT-029。
132
+ - [deferred-item-exit](../../core/deferred-item-exit.md):被延後的項目必須離開它所在的文件。本技能從那一條結束的地方開始。
133
+ - [turn-completion-integrity](../../core/turn-completion-integrity.md):檢查「說了卻沒做」的承諾。與第 5 步的報告不同,它可以擋住回合。
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "universal-dev-standards",
3
- "version": "6.14.0",
3
+ "version": "6.14.1",
4
4
  "description": "Skills for development standards: commit messages, code review, testing, documentation, and more, covering the full development lifecycle.",
5
5
  "author": {
6
6
  "name": "AsiaOstrich",
@@ -49,6 +49,7 @@ These skills provide standard guidance and workflows. They can be accessed via s
49
49
  | `refactoring-assistant` | `/refactor` | [UDS] Refactoring guidance |
50
50
  | `project-discovery` | `/discover` | [UDS] Assess project health and risks |
51
51
  | `brainstorm-assistant` | `/brainstorm` | [UDS] Structured AI-assisted ideation |
52
+ | `open-work-assistant` | `/open-work` | [UDS] Optional: keep work from getting lost between sessions (a cheap capture point, a release condition for each wait, next steps that name something) |
52
53
  | `comprehension-ladder` | `/comprehend` | [UDS] Re-form a hard-to-follow AI output as controlled text, a Mermaid diagram, or an offline HTML explainer, without changing the facts |
53
54
  | `changelog-guide` | `/changelog` | [UDS] Generate changelog entries |
54
55
  | `dev-workflow-guide` | `/dev-workflow` | [UDS] Map development phases to UDS commands |
@@ -90,7 +91,7 @@ These skills provide standard guidance and workflows. They can be accessed via s
90
91
  ### Tier 3 — Specialist (monthly or event-driven)
91
92
  **Listing default**: `"name-only"` in reference overrides — saves tokens; **still callable via `/<name>`**.
92
93
 
93
- `incident-response-assistant`, `observability-assistant`, `slo-assistant`, `runbook-assistant`, `retrospective-assistant`, `durable-execution-assistant`, `metrics-dashboard-assistant`, `migration-assistant`, `security-scan-assistant`, `brainstorm-assistant`, `skill-builder`
94
+ `incident-response-assistant`, `observability-assistant`, `slo-assistant`, `runbook-assistant`, `retrospective-assistant`, `durable-execution-assistant`, `metrics-dashboard-assistant`, `migration-assistant`, `security-scan-assistant`, `brainstorm-assistant`, `skill-builder`, `open-work-assistant`
94
95
 
95
96
  > Tier rationale & criteria: [`flows/skill-tiering-rationale.md`](../flows/skill-tiering-rationale.md). Adopters may freely override the reference (promote a Tier 3 skill to `"on"` if they use it daily, or demote any to `"name-only"`).
96
97
 
@@ -12,7 +12,7 @@ argument-hint: "[phase name | scenario | 階段名稱 | 場景]"
12
12
 
13
13
  # Development Workflow Guide | 開發工作流程指南
14
14
 
15
- > **Language**: English | [繁體中文](../../locales/zh-TW/skills/dev-workflow-guide/SKILL.md)
15
+ > **Language**: English | [繁體中文](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/locales/zh-TW/skills/dev-workflow-guide/SKILL.md)
16
16
 
17
17
  Map your current software development phase to the right UDS commands and skills. Get instant guidance on which tools to use at each stage of development.
18
18
 
@@ -201,9 +201,9 @@ After `/dev-workflow` completes, the AI assistant should suggest based on user's
201
201
  ## References | 參考
202
202
 
203
203
  - [Detailed Phase Guide](./workflow-phases.md) - Complete phase-by-phase reference
204
- - [Daily Workflow Guide](../../adoption/DAILY-WORKFLOW-GUIDE.md) - Comprehensive daily workflow guide
205
- - [Feature Development Workflow](../workflows/feature-dev.workflow.yaml) - Automated feature dev workflow
206
- - [Integrated Flow Workflow](../workflows/integrated-flow.workflow.yaml) - Full ATDD/SDD/BDD/TDD workflow
204
+ - [Daily Workflow Guide](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/adoption/DAILY-WORKFLOW-GUIDE.md) - Comprehensive daily workflow guide
205
+ - [Feature Development Workflow](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/skills/workflows/feature-dev.workflow.yaml) - Automated feature dev workflow
206
+ - [Integrated Flow Workflow](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/skills/workflows/integrated-flow.workflow.yaml) - Full ATDD/SDD/BDD/TDD workflow
207
207
 
208
208
  ---
209
209
 
@@ -0,0 +1,127 @@
1
+ ---
2
+ name: open-work
3
+ scope: universal
4
+ description: |
5
+ [UDS] Optional help for work that stays open across sessions: a cheap capture point, a release condition for every wait, a next step that names something real.
6
+ Use when: work gets lost between sessions, an item has "waited" for days with no known reason, a next step reads only "continue".
7
+ Not for: projects that already track work in an issue tracker or board and lose nothing; planning a feature — use /plan or /sdd.
8
+ Keywords: open work, backlog, inbox, waiting, release condition, next action, 開放工作, 待辦追蹤, 收件匣, 等待中, 解除條件.
9
+ allowed-tools: Read, Glob, Grep, Write, Bash
10
+ argument-hint: "[capture | waiting | next-action | report | 收件 | 等待 | 下一步 | 報告]"
11
+ ---
12
+
13
+ # Open Work | 開放工作追蹤
14
+
15
+ > **Language**: English | [繁體中文](../../locales/zh-TW/skills/open-work-assistant/SKILL.md) | [简体中文](../../locales/zh-CN/skills/open-work-assistant/SKILL.md)
16
+
17
+ **Version**: 1.0.0 | **Last Updated**: 2026-10-30 | **Applicability**: Claude Code Skills
18
+
19
+ Help keep work from getting lost between sessions. Use it when you want it. Nothing in UDS requires it.
20
+
21
+ ## Purpose
22
+
23
+ This skill used to be a standard, `open-work-tracking`. UDS moved it here because the standard was tried on one project, and that project's own use did not confirm it. A skill fits better: you pick it up when work is getting lost, and you leave it when it is not.
24
+
25
+ The full text of the old standard is kept as a reference document: [open-work-tracking](../../core/open-work-tracking.md). UDS does not install it any more. This skill holds the part that was worth keeping.
26
+
27
+ ## When to use it, and when not
28
+
29
+ First find out which problem is real. Ask the user. Do not start a tracker for a problem nobody has.
30
+
31
+ | What goes wrong | What helps |
32
+ |---|---|
33
+ | A new idea comes up in the middle of a task, and there is no cheap place to put it | A capture point that costs two fields |
34
+ | An item is paused "waiting", and later nobody knows for what | A release condition written next to the wait |
35
+ | A planned item is not started, time passes, and nothing points back at it | A date, or a regular look at the list |
36
+
37
+ If none of the three is real, stop and say so. If the project already has an issue tracker or a project board and loses nothing there, keep using it. A second list that nobody reads is a new place to lose work.
38
+
39
+ ## Workflow
40
+
41
+ ### 1. Capture: two fields
42
+
43
+ Write the date and one sentence. Nothing else.
44
+
45
+ | Date | What |
46
+ |---|---|
47
+ | 2026-10-30 | Check whether the export job still runs after the schema change |
48
+
49
+ Do not ask for a category, a priority or an owner at this step. Those are decided later, when the list is sorted. A third required field makes people stop using the list.
50
+
51
+ ### 2. Waiting: write what releases it
52
+
53
+ Every item marked "waiting" gets two things: what it waits for, and what event ends the wait. Prefer an event a machine can see: a date, a file that appears, a tag, an identifier.
54
+
55
+ | Item | Status | asked-at | Waiting for | Release |
56
+ |---|---|---|---|---|
57
+ | Vendor quote | asked-awaiting | 2026-10-27 | The vendor's reply | A file `quotes/vendor-a.md` exists |
58
+
59
+ Say which kind of waiting it is:
60
+
61
+ - `not-yet-asked`: the request is drafted or decided, and nobody has sent it. Name the draft or command whose sending releases it.
62
+ - `asked-awaiting`: it was sent, and nothing has come back. Write `asked-at` (a full date with the year). An item with an age can come back on a threshold. An item without one cannot.
63
+
64
+ If the wait is for something in another project, write `<project>:<object>`, for example `uds:v6.15.0` or `vibeops:docs/handoff.md`. The project is a logical name, never a directory on one machine.
65
+
66
+ ### 3. Next step: name something
67
+
68
+ A next step names at least one thing a reader can go and find: a file path, a test name, a command, or a requirement identifier. "Continue" and "handle the rest" name nothing.
69
+
70
+ | Weak | Better |
71
+ |---|---|
72
+ | Continue the migration | Run `npm run migrate -- --dry-run` and read `migrations/0042.sql` |
73
+
74
+ An item that was asked and awaits a reply may use the reply as its next step. Then it needs `asked-at`, what it waits for, and what releases it.
75
+
76
+ ### 4. Sort the list: three exits
77
+
78
+ Sort the captured items on a regular day. Each item goes to one of three places:
79
+
80
+ 1. It becomes a spec or a tracked item.
81
+ 2. It goes on the list of work to do.
82
+ 3. It is dropped, with one sentence that says why.
83
+
84
+ An item that stays unsorted for more than about two weeks is named in the report. A drop without a reason looks the same as an item that was deleted by mistake.
85
+
86
+ ### 5. Report: say what you could not see
87
+
88
+ When you report "N items are open", also say how many sources you looked at and how many you could not. An unseen source is not zero. A report without that sentence reads as complete.
89
+
90
+ Print the report when a turn ends and control goes back to the person. The report must never block the turn. "Some work is still open" is nearly always true, and a check that is always red gets switched off.
91
+
92
+ ### 6. Facts you cannot see
93
+
94
+ Some facts have no source an assistant can read: was a message sent, did the other side reply, was it approved. Write them by hand only with three things: who saw it (`observed-by`), when (`observed-at`, with the year), and a value of `yes`, `no` or `unknown`. `unknown` is a real value. It is counted apart and never counted as done. Show the age of every observation. A stamp says someone saw it once. It does not say it is still true.
95
+
96
+ Do not hand-write what version control, a spec marker or a CI result already says.
97
+
98
+ ### 7. Optional: run the reference checks
99
+
100
+ UDS ships a reference checker for these rules in the CLI:
101
+
102
+ ```bash
103
+ uds open-work next-action [files...] # does every next step name something?
104
+ uds open-work waiting [files...] # does every wait have a release condition?
105
+ uds open-work observations [files...] # are the hand-written facts stamped?
106
+ uds open-work self-test # does the checker itself still fail on a bad sample?
107
+ ```
108
+
109
+ The checker finds fields by their column names, such as `status`, `asked-at`, `waiting for` and `release` (the tables above use them). If your tables use other words, declare them in `uds.project.yaml` under `open_work`.
110
+
111
+ Exit code 0 means no violation, 1 means a violation, 2 means the checker could not decide. 2 is not a pass. A clean run covers only the words it recognised. The vocabulary is a first guess and has not been tuned on real use.
112
+
113
+ ## Where to keep it
114
+
115
+ Anywhere your project already looks: an issue tracker, a project board, a file in the repository. UDS does not choose for you. Two properties matter: the place is under version control or otherwise readable by every session that needs it, and it is not only in one person's private assistant memory. Work that waits on another project must be recorded where the sessions of both projects can read it.
116
+
117
+ ## What this skill does not claim
118
+
119
+ - The rules above came from one project. UDS has no evidence that they work for other projects.
120
+ - The thresholds (two fields, two weeks, seven days for a stale observation) are first judgments, not measurements.
121
+ - The checker reads the structure of tables and lists. It cannot tell whether a note is true.
122
+
123
+ ## Related
124
+
125
+ - [open-work-tracking](../../core/open-work-tracking.md): the former standard, now reference only. Its requirements are numbered OWT-001 to OWT-029.
126
+ - [deferred-item-exit](../../core/deferred-item-exit.md): an item that is deferred must leave its document. This skill starts where that one ends.
127
+ - [turn-completion-integrity](../../core/turn-completion-integrity.md): the check for a promise that was stated and dropped. Unlike the report in step 5, it may block a turn.