docs(sdlc): translate SKILL.md into English per guidelines

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

skills/maintain/SKILL.md

@@ -3,24 +3,24 @@ name: maintain
 description: SDLC maintenance stage. Gate on model capability tags, read projects still inside their maintenance window from MAINTAIN_CONTENTS, then run one sub agent per project: switch to develop or master, propose at least five maintenance actions, commit to a new branch, push, and PR. Update the last-maintained timestamp afterward. Use for periodic upkeep of delivered projects.
 ---
 
-# maintain — 維護
+# maintain
 
-目標：逐項完成維護目錄內專案的例行維護。
-所有 wiki 讀寫一律經由 `jsc-gitea:wiki`。
+Goal: run routine maintenance for every project in the maintenance contents page.
+All wiki reads and writes go through `jsc-gitea:wiki`.
 
-## 流程
+## Steps
 
-1. **模型能力檢查**：依 `jsc-cli:models` 的「SDLC 階段需求」表確認目前模型適合維護階段（維護接受任意標籤，但模型必須列於對照表）。不適合就阻擋流程，並告知使用者建議改用的模型。
-2. 經由 `jsc-gitea:wiki` 讀取 `MAINTAIN_CONTENTS`，篩出**仍在維護期間內**的專案：維護起始日 ≤ 今天，且（維護截止日為 NULL 或 ≥ 今天）。
-3. 每一個專案**必須啟動一個 sub agent** 依以下流程執行：
-   1. 將專案切換到 `develop` 分支，沒有就切 `master`，並更新到最新。
-   2. 提供**至少五種**建議的維護方法，依專案狀況取捨執行，例如：
-      - 相依套件更新（複用 `jsc-pkg:pkg-update`）
-      - 安全性弱點掃描與修補
-      - 死碼與過期註解清理
-      - 測試覆蓋率補強
-      - 文件與 README 同步
-      - 建置警告消除
-   3. 依 `jsc-git:commit` 把變更 commit 到新分支，push 後依 `jsc-git:pr` 建立 PR 回 develop 或 master。
-   4. 更新 `MAINTAIN_CONTENTS` 中該專案的「前次維護時間」為今天。
-4. 主 agent 彙整回報：每個專案執行了哪些維護方法、PR 連結、失敗原因。
+1. **Model capability gate**: check the 「SDLC 階段需求」 table from `jsc-cli:models` and confirm the current model qualifies for maintenance (any tag qualifies, but the model must be listed in the mapping table). If not, block the flow and tell the user which model to switch to.
+2. Read `MAINTAIN_CONTENTS` via `jsc-gitea:wiki` and filter projects **still inside their maintenance window**: start date ≤ today, and (end date is NULL or ≥ today).
+3. Every project **MUST run as a sub agent** with this flow:
+   1. Switch the project to the `develop` branch, falling back to `master`, and pull to latest.
+   2. Propose **at least five** maintenance methods and apply the ones that fit the project, for example:
+      - dependency updates (reuse `jsc-pkg:pkg-update`)
+      - security vulnerability scan and patching
+      - dead code and stale comment cleanup
+      - test coverage reinforcement
+      - docs and README synchronization
+      - build warning elimination
+   3. Commit the changes to a new branch per `jsc-git:commit`, push, then open a PR back to develop or master per `jsc-git:pr`.
+   4. Update the project's last-maintained field (the zh-TW column 「前次維護時間」) in `MAINTAIN_CONTENTS` to today.
+4. The main agent reports the summary: maintenance methods applied per project, PR links, and failure reasons. The report and all generated wiki content, commits, and PR descriptions stay Traditional Chinese per the STE100 rule.