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

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

skills/plan/SKILL.md

@@ -3,29 +3,29 @@ name: plan
 description: SDLC planning stage. Gate on model capability tags, pick or create a plan from PLAN_CONTENTS, then run a decision tree until goal, scope, and feasibility reach consensus. Produce user stories into wiki page PLAN_{yyyyMMdd}_{HHmmss}_{HASH}. Logic only - never write code or modify files. Use when the user wants to start or refine a plan; not for analysis or implementation.
 ---
 
-# plan — 規劃
+# plan
 
-目標：產出或補充 WIKI 計畫頁 `PLAN_{yyyyMMdd}_{HHmmss}_{HASH}`。
-本技能是**純邏輯**階段：不可以出現任何程式碼，也**禁止修改任何檔案**。
+Goal: create or extend the wiki plan page `PLAN_{yyyyMMdd}_{HHmmss}_{HASH}`.
+This skill is a **logic-only** stage: never output code, and **never modify any file**.
 
-`{HASH}` = `{owner}/{repo}` 的 SHA-1 前 8 碼、大寫。
-所有 wiki 讀寫一律經由 `jsc-gitea:wiki`。
+`{HASH}` = first 8 chars of the SHA-1 of `{owner}/{repo}`, uppercase.
+All wiki reads and writes go through `jsc-gitea:wiki`.
 
-## 流程
+## Steps
 
-1. **模型能力檢查**：依 `jsc-cli:models` 的能力標籤確認目前模型具備「規劃」能力。不適合就阻擋流程，並告知使用者建議改用的模型。
-2. 經由 `jsc-gitea:wiki` 讀取 `PLAN_CONTENTS`，列出**未分析**的計畫名稱與 HASH。
-3. 依 `jsc-ask:ask` 規則讓使用者選擇：**補充既有計畫**（列出未分析計畫為選項）或**新建計畫**。每個選項標明影響範圍。
-4. 依 `jsc-ask:ask` 決策樹詢問，補全以下三項直到沒有疑慮；只要還沒達成共識就繼續詢問：
-   - 計畫目標：要解決什麼問題、成功的判斷標準。
-   - 計畫範圍：包含什麼、排除什麼、涉及哪些存取庫。
-   - 可行性：系統架構與資料來源是否支撐目標。
-5. 由共識產生**使用者故事**（身為⋯⋯我想要⋯⋯以便⋯⋯），逐條列出。
-6. 套用 `templates/plan-page.md` 產生或更新計畫頁，經由 `jsc-gitea:wiki` 寫回。
-7. 若是新的計畫頁，套用 `templates/plan-contents.md` 的條目格式，將其加入 `PLAN_CONTENTS`（狀態=未分析）。
+1. **Model capability gate**: check the capability tags from `jsc-cli:models` and confirm the current model qualifies for planning. If not, block the flow and tell the user which model to switch to.
+2. Read `PLAN_CONTENTS` via `jsc-gitea:wiki` and list the plans whose status is the literal 「未分析」 (not analyzed), with names and HASH.
+3. Let the user choose per `jsc-ask:ask` rules: **extend an existing plan** (list the not-analyzed plans as options) or **create a new plan**. State the impact scope on every option.
+4. Question via the `jsc-ask:ask` decision tree until no doubt remains on all three items; keep asking while consensus is missing:
+   - Goal: the problem to solve and the criteria for success.
+   - Scope: what is included, what is excluded, which repositories are involved.
+   - Feasibility: whether the system architecture and data sources support the goal.
+5. Turn the consensus into **user stories** (the zh-TW pattern 「身為⋯⋯我想要⋯⋯以便⋯⋯」), one per line.
+6. Apply `templates/plan-page.md` to create or update the plan page, and write it back via `jsc-gitea:wiki`. The page content is Traditional Chinese, exactly as the template dictates.
+7. If the plan page is new, add it to `PLAN_CONTENTS` using the entry format of `templates/plan-contents.md`, with status set to the literal 「未分析」.
 
-## 禁止事項
+## Hard limits
 
-- 不可輸出任何程式碼片段。
-- 不可修改工作目錄的任何檔案。
-- 不可跳過決策樹直接假設需求。
+- Never output a code snippet.
+- Never modify any file in the working directory.
+- Never skip the decision tree and assume requirements.