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

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

skills/implement/SKILL.md

@@ -3,24 +3,25 @@ name: implement
 description: SDLC implementation stage. Gate on model capability tags, claim a ready work package from ANALYZE_CONTENTS with a work ticket, then complete its TDD todos one by one, updating the wiki after every item. Ends with jsc-review code-review and an optional MAINTAIN_CONTENTS entry. Use when analysis is done and code must be written; not for planning or analysis.
 ---
 
-# implement — 實作
+# implement
 
-目標：逐項完成分析頁的待辦事項；**每完成一項就必須立即更新 WIKI 狀態**。
-所有 wiki 讀寫一律經由 `jsc-gitea:wiki`。
+Goal: complete the analysis page's todos one by one; **update the wiki status immediately after every completed item**.
+All wiki reads and writes go through `jsc-gitea:wiki`.
 
-## 流程
+## Steps
 
-1. **模型能力檢查**：依 `jsc-cli:models` 的能力標籤確認目前模型具備「實作」能力。不適合就阻擋流程，並告知使用者建議改用的模型。
-2. **產生工作證**：格式 `TICKET_{session id 前 8 碼}_{yyyyMMddHHmmss}`，並嘗試將目前 session 重新命名為工作證名稱（CLI 不支援時略過）。
-3. 經由 `jsc-gitea:wiki` 讀取 `ANALYZE_CONTENTS`，列出未完成的：計畫名稱、HASH、工作包編號、未完成項目數量。可選的工作包必須同時滿足：**未完成、無相依（或相依都已完成）、無工作證**。
-4. 依 `jsc-ask:ask` 規則讓使用者選擇要實作的工作包（選項標明未完成項目數與預估工時）。把工作證寫入分析頁該工作包的「工作證」欄位並寫回 wiki，**成功標上工作證才可以進入下一步**。
-5. 列出該工作包所有未完成項目，**逐項實作**：
-   - 依 TDD 循環：先紅後綠、一次一片；規則與反模式見 `references/tdd.md`（重構留給審查階段）。
-   - 每完成一項，立即把分析頁該項 `[ ]` 改為 `[x]` 並寫回 wiki，才可以進行下一項。
-6. 全部完成後呼叫 `jsc-review:code-review` 等待程式碼審查；審查未過就修正並重新審查。
-7. 依 `jsc-ask:ask` 規則詢問是否將本專案加入維護：套用 `templates/maintain-contents.md` 加入 `MAINTAIN_CONTENTS`。必填：存取庫名稱 `{owner}/{repo}`、維護方式、維護起始日。選填：維護截止日（NULL = 永久維護）、前次維護時間。
+1. **Model capability gate**: check the capability tags from `jsc-cli:models` and confirm the current model qualifies for implementation. If not, block the flow and tell the user which model to switch to.
+2. **Generate a work ticket**: format `TICKET_{first 8 chars of session id}_{yyyyMMddHHmmss}`. Try to rename the current session to the ticket name (skip when the CLI does not support it).
+3. Read `ANALYZE_CONTENTS` via `jsc-gitea:wiki` and list what is unfinished: plan name, HASH, work package number, count of open items. A selectable work package must satisfy all three: **unfinished, dependency-free (or all dependencies done), and not holding a work ticket**.
+4. Let the user pick a work package per `jsc-ask:ask` rules (options state open-item count and estimated effort). Write the ticket into that work package's ticket column (the zh-TW field 「工作證」) on the analysis page and save it back to the wiki. **Only after the ticket is saved successfully may you proceed.**
+5. List every open item of the work package and implement them **one at a time**:
+   - Follow the TDD loop: red before green, one slice at a time; rules and anti-patterns in `references/tdd.md` (refactoring belongs to the review stage).
+   - After each item, flip its `[ ]` to `[x]` on the analysis page and save to the wiki before starting the next item.
+6. When all items are done, call `jsc-review:code-review` and wait for the review; on failure, fix and re-review until it passes.
+7. Ask per `jsc-ask:ask` rules whether to register this project for maintenance: append to `MAINTAIN_CONTENTS` with `templates/maintain-contents.md`. Required: repository `{owner}/{repo}`, maintenance method, start date. Optional: end date (NULL = maintain forever), last-maintained time.
 
-## 規則
+## Rules
 
-- 工作證是互斥鎖：看到已有工作證的工作包一律跳過，不可搶占。
-- 不可一次完成多項才批次更新 wiki；一項一更新。
+- The work ticket is a mutex: always skip work packages that already hold a ticket; never take one over.
+- Never batch wiki updates across items; one item, one update.
+- Everything the skill writes out (wiki content, commit messages, PR descriptions) stays Traditional Chinese per the STE100 rule.