@fitlab-ai/agent-infra 0.5.1 → 0.5.3

package/templates/.agents/skills/cancel-task/{SKILL.md → SKILL.en.md}

@@ -7,9 +7,9 @@ description: "Cancel an unneeded task and archive it"
 
 ## Boundary / Critical Rules
 
-- This command terminates a task that no longer needs to continue and archives it into `completed/`
+- This command terminates a task that no longer needs to continue and moves it into `completed/`
 - Cancel only when the task no longer needs implementation, review, or follow-up work
-- When a valid `issue_number` exists, GitHub Issue sync is required
+- When a valid `issue_number` exists, Issue sync is required
 
 ## Steps
 
@@ -22,12 +22,12 @@ Check these directories in order:
 
 Handling rules:
 - If found in `active/` or `blocked/`: continue
-- If found only in `completed/`: inform the user the task is already archived and stop
+- If found only in `completed/`: inform the user the task is already moved and stop
 - If not found anywhere: prompt `Task {task-id} not found`
 
 ### 2. Choose the Cancellation Label
 
-Infer the GitHub Issue closing label from the cancellation reason:
+Infer the Issue closing label from the cancellation reason:
 - `status: superseded`: reason implies duplicate, replaced, merged into, or already covered by another Issue or PR
 - `status: invalid`: reason implies invalid report, no real problem, cannot reproduce, or no issue after investigation
 - `status: declined`: reason implies not planned, deprioritized, or explicitly rejected
@@ -40,7 +40,7 @@ When syncing to the Issue, replace any existing `status:` labels with the inferr
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `task.md` in the task directory:
@@ -50,16 +50,16 @@ Update `task.md` in the task directory:
 - `updated_at`: {current timestamp}
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Cancelled** by {agent} — {one-line cancellation reason}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Cancelled** by {agent} — {one-line cancellation reason}
   ```
 
-### 4. Archive the Task
+### 4. Move the Task
 
 Move the task directory into `.agents/workspace/completed/{task-id}`.
 
 If the source directory is `blocked/`, move it from `blocked/`; if it is `active/`, move it from `active/`.
 
-### 5. Verify the Archive
+### 5. Verify the Move
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.md
@@ -72,6 +72,7 @@ Confirm the task directory was moved successfully.
 Check whether `task.md` contains a valid `issue_number`. If not, skip this step.
 
 > Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+> Read `.agents/rules/issue-pr-commands.md` before closing the Issue.
 
 If a valid `issue_number` exists:
 - Replace all `status:` labels with the label inferred in Step 2
@@ -80,7 +81,7 @@ If a valid `issue_number` exists:
 - Remove all assignees
 - Publish a cancellation comment using the marker `<!-- sync-issue:{task-id}:cancel -->`
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment using the task-comment sync rules from `.agents/rules/issue-sync.md`
-- Close the Issue: `gh issue close {issue-number} --reason "not planned"`
+- Close the Issue by following the "Close an Issue" command in `.agents/rules/issue-pr-commands.md`, using the fixed reason `not planned`
 
 The cancellation comment must include at least:
 - the cancellation reason
@@ -88,7 +89,7 @@ The cancellation comment must include at least:
 
 ### 7. Verification Gate
 
-Run the verification gate to confirm the archived task and sync state are valid:
+Run the verification gate to confirm the moved task and sync state are valid:
 
 ```bash
 node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/completed/{task-id} --format text
@@ -109,13 +110,13 @@ Keep the gate output in your reply as fresh evidence. Do not claim completion wi
 
 Output format:
 ```
-Task {task-id} cancelled and archived.
+Task {task-id} cancelled; task directory moved to completed/.
 
 Cancellation reason: {reason}
-GitHub label: {status-label or skipped}
-Archived to: .agents/workspace/completed/{task-id}/
+Status label: {status-label or skipped}
+Target path: .agents/workspace/completed/{task-id}/
 
-Next step - inspect the archived task:
+Next step - inspect the moved task:
   - Claude Code / OpenCode: /check-task {task-id}
   - Gemini CLI: /{{project}}:check-task {task-id}
   - Codex CLI: $check-task {task-id}
@@ -125,7 +126,7 @@ Next step - inspect the archived task:
 
 - [ ] Recorded the cancellation reason and updated task.md
 - [ ] Moved the task directory into `.agents/workspace/completed/`
-- [ ] Completed GitHub sync when an Issue exists
+- [ ] Completed Issue sync when an Issue exists
 - [ ] Ran and passed the verification gate
 - [ ] Showed the full next-step command set to the user
 
@@ -138,5 +139,5 @@ Next step - inspect the archived task:
 ## Error Handling
 
 - Task not found: `Task {task-id} not found`
-- Task already archived: inform the user it is already in `completed/`
-- Issue sync failed: keep the local archive result and tell the user manual GitHub follow-up is required
+- Task already moved: inform the user it is already in `completed/`
+- Issue sync failed: keep the local move result and tell the user manual platform follow-up is required

package/templates/.agents/skills/cancel-task/SKILL.zh-CN.md

@@ -7,9 +7,9 @@ description: "取消不再需要的任务并归档"
 
 ## 行为边界 / 关键规则
 
-- 本命令用于终止一个不再需要继续执行的任务，并归档到 `completed/`
+- 本命令用于终止一个不再需要继续执行的任务，并转移到 `completed/`
 - 只有在确认该任务无需继续实现、审查或修复时才可取消
-- 有效 `issue_number` 存在时，GitHub Issue 同步属于必做项
+- 有效 `issue_number` 存在时，Issue 同步属于必做项
 
 ## 执行步骤
 
@@ -22,12 +22,12 @@ description: "取消不再需要的任务并归档"
 
 处理规则：
 - 如果在 `active/` 或 `blocked/` 中找到：继续
-- 如果只在 `completed/` 中找到：告知用户任务已归档，停止
+- 如果只在 `completed/` 中找到：告知用户任务已转移，停止
 - 如果都不存在：提示 `Task {task-id} not found`
 
 ### 2. 判断取消标签
 
-根据取消原因推断 GitHub Issue 关闭标签：
+根据取消原因推断 Issue 关闭标签：
 - `status: superseded`：原因包含“重复”、“替代”、“合并到”、“已由 #123 / PR 替代”等语义
 - `status: invalid`：原因包含“误报”、“不存在”、“无法复现”、“排查后无问题”等语义
 - `status: declined`：原因包含“不做”、“暂不实现”、“优先级调整”、“方案否决”等语义
@@ -40,7 +40,7 @@ description: "取消不再需要的任务并归档"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新任务目录中的 `task.md`：
@@ -50,16 +50,16 @@ date "+%Y-%m-%d %H:%M:%S"
 - `updated_at`：{当前时间戳}
 - **追加**到 `## Activity Log`（不要覆盖之前记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Cancelled** by {agent} — {一行取消原因}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Cancelled** by {agent} — {一行取消原因}
   ```
 
-### 4. 归档任务
+### 4. 转移任务
 
 将任务目录移动到 `.agents/workspace/completed/{task-id}`。
 
 如果源目录在 `blocked/`，从 `blocked/` 移动；如果源目录在 `active/`，从 `active/` 移动。
 
-### 5. 验证归档
+### 5. 验证转移
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.md
@@ -72,6 +72,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤。
 
 > Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+> 关闭 Issue 前先读取 `.agents/rules/issue-pr-commands.md`。
 
 如果存在有效的 `issue_number`：
 - 替换所有 `status:` labels，并设置步骤 2 推断出的标签
@@ -80,7 +81,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 - 移除全部 assignees
 - 发布取消评论，隐藏标记使用 `<!-- sync-issue:{task-id}:cancel -->`
 - 使用 `.agents/rules/issue-sync.md` 的 task.md 评论同步规则创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论
-- 关闭 Issue：`gh issue close {issue-number} --reason "not planned"`
+- 关闭 Issue：按 `.agents/rules/issue-pr-commands.md` 中的“关闭 Issue”命令执行，关闭原因固定为 `not planned`
 
 取消评论至少包含：
 - 取消原因
@@ -88,7 +89,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 ### 7. 完成校验
 
-运行完成校验，确认任务归档和同步状态符合规范：
+运行完成校验，确认任务转移和同步状态符合规范：
 
 ```bash
 node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/completed/{task-id} --format text
@@ -109,13 +110,13 @@ node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/com
 
 输出格式：
 ```
-任务 {task-id} 已取消并归档。
+任务 {task-id} 已取消，任务目录已转移到 completed/。
 
 取消原因：{reason}
-GitHub 标签：{status-label 或 skipped}
-归档路径：.agents/workspace/completed/{task-id}/
+状态标签：{status-label 或 skipped}
+目标路径：.agents/workspace/completed/{task-id}/
 
-下一步 - 查看归档任务：
+下一步 - 查看已转移任务：
   - Claude Code / OpenCode：/check-task {task-id}
   - Gemini CLI：/{{project}}:check-task {task-id}
   - Codex CLI：$check-task {task-id}
@@ -125,7 +126,7 @@ GitHub 标签：{status-label 或 skipped}
 
 - [ ] 已记录取消原因并更新 task.md
 - [ ] 已将任务目录移动到 `.agents/workspace/completed/`
-- [ ] 已在存在 Issue 时完成 GitHub 同步
+- [ ] 已在存在 Issue 时完成 Issue 同步
 - [ ] 已运行 gate 校验并通过
 - [ ] 已向用户展示完整的下一步命令
 
@@ -138,5 +139,5 @@ GitHub 标签：{status-label 或 skipped}
 ## 错误处理
 
 - 任务未找到：`Task {task-id} not found`
-- 任务已归档：提示任务已在 `completed/` 中
-- Issue 同步失败：保留本地归档结果，并告知用户需要人工补齐 GitHub 操作
+- 任务已转移：提示任务已在 `completed/` 中
+- Issue 同步失败：保留本地转移结果，并告知用户需要人工补齐平台操作

package/templates/.agents/skills/close-codescan/{SKILL.md → SKILL.en.md}

@@ -11,9 +11,7 @@ Dismiss the specified Code Scanning (CodeQL) alert and record a justified reason
 
 ### 1. Retrieve Alert Information
 
-```bash
-gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
-```
+Read `.agents/rules/security-alerts.md` before this step, then use its Code Scanning alert read command to fetch the alert details.
 
 Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
@@ -61,13 +59,7 @@ Confirm? (y/N)
 
 ### 6. Execute the Dismissal
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/code-scanning/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{user explanation}"
-```
+Dismiss the alert by following the Code Scanning dismiss command in `.agents/rules/security-alerts.md`, passing the mapped `{api-reason}` and the user's explanation.
 
 **API reason mapping** (per the GitHub Code Scanning API):
 - False Positive -> `false positive`
@@ -80,13 +72,13 @@ If a related task exists (search for `codescan_alert_number: <alert-number>`):
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 - Add the dismissal record to task.md
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
   ```
 - Archive the task
 
@@ -115,7 +107,7 @@ Next step - complete and archive the task if a related task exists:
 ## Notes
 
 1. **Handle high-severity alerts carefully**: Critical/High alerts require thorough analysis. Prefer `import-codescan` + `analyze-task` first.
-2. **Use truthful reasons**: dismissal records are stored in GitHub and may be audited.
+2. **Use truthful reasons**: dismissal records are stored on the platform and may be audited.
 3. **Review periodically**: dismissed alerts should be re-evaluated over time.
 4. **Fix first**: dismissal should be the last resort.
 

package/templates/.agents/skills/close-codescan/SKILL.zh-CN.md

@@ -11,9 +11,7 @@ description: "关闭 Code Scanning 告警并记录理由"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Code Scanning 告警读取命令获取告警详情。
 
 验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
 
@@ -61,13 +59,7 @@ Code Scanning 告警 #{alert-number}
 
 ### 6. 执行关闭
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/code-scanning/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{用户的说明}"
-```
+按 `.agents/rules/security-alerts.md` 中的 Code Scanning 告警关闭命令执行关闭操作，并传入映射后的 `{api-reason}` 与用户说明。
 
 **API reason 映射**（按 GitHub Code Scanning API）：
 - 误报 -> `false positive`
@@ -80,13 +72,13 @@ gh api --method PATCH \
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 - 添加关闭记录到 task.md
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
   ```
 - 归档任务
 
@@ -115,7 +107,7 @@ Code Scanning 告警 #{alert-number} 已关闭。
 ## 注意事项
 
 1. **谨慎处理高严重程度告警**：Critical/High 告警需要充分分析。建议先执行 import-codescan + analyze-task。
-2. **真实的理由**：关闭记录保存在 GitHub 中，可能会被审计。
+2. **真实的理由**：关闭记录保存在平台中，可能会被审计。
 3. **定期复查**：已关闭的告警应定期复查。
 4. **优先修复**：关闭应作为最后手段。
 

package/templates/.agents/skills/close-dependabot/{SKILL.md → SKILL.en.md}

@@ -11,9 +11,7 @@ Dismiss the specified Dependabot security alert and record a justified reason.
 
 ### 1. Retrieve Alert Information
 
-```bash
-gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
-```
+Read `.agents/rules/security-alerts.md` before this step, then use its Dependabot alert read command to fetch the alert details.
 
 Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
@@ -67,13 +65,7 @@ Confirm? (y/N)
 
 ### 6. Execute the Dismissal
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/dependabot/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{user explanation}"
-```
+Dismiss the alert by following the Dependabot dismiss command in `.agents/rules/security-alerts.md`, passing the mapped `{api-reason}` and the user's explanation.
 
 **API reason mapping**:
 - False Positive -> `not_used` or `inaccurate`
@@ -88,13 +80,13 @@ If a related task exists (search for `security_alert_number: <alert-number>`):
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 - Add the dismissal record to task.md
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
   ```
 - Archive the task
 
@@ -110,9 +102,9 @@ Severity: {severity}
 Reason: {reason}
 Explanation: {explanation}
 
-View: https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
+View: {alert-url}
 
-Note: it can be reopened on GitHub if necessary.
+Note: it can be reopened on the platform if necessary.
 
 Next step - complete and archive the task if a related task exists:
   - Claude Code / OpenCode: /complete-task {task-id}
@@ -123,7 +115,7 @@ Next step - complete and archive the task if a related task exists:
 ## Notes
 
 1. **Handle high-severity alerts carefully**: Critical/High alerts require thorough analysis before dismissal. Prefer `import-dependabot` + `analyze-task` first.
-2. **Use truthful reasons**: dismissal records are stored in GitHub and may be audited.
+2. **Use truthful reasons**: dismissal records are stored on the platform and may be audited.
 3. **Review periodically**: dismissed alerts should be re-evaluated because code changes may invalidate the dismissal rationale.
 4. **Fix first**: dismissal should be the last resort. Prefer upgrading, replacing, or mitigating.
 

package/templates/.agents/skills/close-dependabot/SKILL.zh-CN.md

@@ -11,9 +11,7 @@ description: "关闭 Dependabot 安全告警并记录理由"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Dependabot 告警读取命令获取告警详情。
 
 验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
 
@@ -67,13 +65,7 @@ CVE：{cve-id}
 
 ### 6. 执行关闭
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/dependabot/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{用户的说明}"
-```
+按 `.agents/rules/security-alerts.md` 中的 Dependabot 告警关闭命令执行关闭操作，并传入映射后的 `{api-reason}` 与用户说明。
 
 **API reason 映射**：
 - 误报 -> `not_used` 或 `inaccurate`
@@ -88,13 +80,13 @@ gh api --method PATCH \
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 - 添加关闭记录到 task.md
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
   ```
 - 归档任务
 
@@ -110,9 +102,9 @@ date "+%Y-%m-%d %H:%M:%S"
 原因：{reason}
 说明：{explanation}
 
-查看：https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
+查看：{alert-url}
 
-注意：如有需要，可在 GitHub 上重新打开。
+注意：如有需要，可在平台侧重新打开。
 
 下一步 - 完成并归档任务（如有关联任务）：
   - Claude Code / OpenCode：/complete-task {task-id}
@@ -123,7 +115,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 注意事项
 
 1. **谨慎处理高严重程度告警**：Critical/High 告警需要在关闭前进行充分分析。建议先执行 import-dependabot + analyze-task。
-2. **真实的理由**：关闭记录保存在 GitHub 中，可能会被审计。
+2. **真实的理由**：关闭记录保存在平台中，可能会被审计。
 3. **定期复查**：已关闭的告警应定期复查，因为代码变更可能使关闭理由失效。
 4. **优先修复**：关闭应作为最后手段。优先考虑升级、替换或缓解。
 

package/templates/.agents/skills/commit/{SKILL.md → SKILL.en.md}

@@ -39,7 +39,7 @@ Stage specific files only and run `git commit` with the prepared message.
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 > The full four-case status matrix, prerequisite checks, and multi-TUI next-step commands live in `reference/task-status-update.md`. Read `reference/task-status-update.md` before updating task state.

package/templates/.agents/skills/commit/SKILL.zh-CN.md

@@ -39,7 +39,7 @@ git diff
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 > 完整的 4 种状态分支、前置条件检查和多 TUI 下一步命令见 `reference/task-status-update.md`。更新任务状态前，先读取 `reference/task-status-update.md`。

package/templates/.agents/skills/commit/reference/{task-status-update.md → task-status-update.en.md}

@@ -7,13 +7,13 @@ Read this file before choosing the post-commit task-state branch.
 Get the current time first:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 For every task-related commit, append this Activity Log entry in `task.md`:
 
 ```text
-- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Commit** by {agent} — {commit hash short} {commit subject}
 ```
 
 Before selecting the next step, verify:

package/templates/.agents/skills/commit/reference/task-status-update.zh-CN.md

@@ -7,13 +7,13 @@
 先获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 对于每一次与任务相关的提交，都要在 `task.md` 中追加以下 Activity Log：
 
 ```text
-- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Commit** by {agent} — {commit hash short} {commit subject}
 ```
 
 在决定下一步之前，先确认：

package/templates/.agents/skills/complete-task/{SKILL.md → SKILL.en.md}

@@ -8,7 +8,7 @@ description: "Mark a task as completed and archive it"
 ## Boundary / Critical Rules
 
 - This command updates task metadata AND physically moves the task directory
-- Do not archive a task that has incomplete workflow steps unless forced
+- Do not move a task that has incomplete workflow steps unless forced
 
 ## Steps
 
@@ -36,7 +36,7 @@ Before marking complete, verify ALL of these:
 > - If any condition is missing -> **stop by default** and output the prerequisite warning
 > - Only continue with unmet prerequisites when the user explicitly requested `--force`
 >
-> **Do not continue to Steps 3-7 when prerequisites are not met, and do not output "Task {task-id} completed and archived."**
+> **Do not continue to Steps 3-7 when prerequisites are not met, and do not output "Task {task-id} completed; task directory moved to completed/."**
 
 If any prerequisite is not met, warn the user:
 ```
@@ -53,7 +53,7 @@ If prerequisites are not met and the user did not explicitly provide `--force`,
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -64,10 +64,10 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - Verify and check off all items in `## Completion Checklist` (change `- [ ]` to `- [x]`)
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Completed** by {agent} — Task moved to completed/
   ```
 
-### 4. Archive Task
+### 4. Move Task
 
 Move the task directory from active to completed:
 
@@ -75,7 +75,7 @@ Move the task directory from active to completed:
 mv .agents/workspace/active/{task-id} .agents/workspace/completed/{task-id}
 ```
 
-### 5. Verify Archive
+### 5. Verify Move
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.md
@@ -116,12 +116,12 @@ Keep the gate output in your reply as fresh evidence. Do not claim completion wi
 
 Output format:
 ```
-Task {task-id} completed and archived.
+Task {task-id} completed; task directory moved to completed/.
 
 Task info:
 - Title: {title}
 - Completed at: {timestamp}
-- Archived to: .agents/workspace/completed/{task-id}/
+- Target path: .agents/workspace/completed/{task-id}/
 
 Deliverables:
 - {List of key outputs: files modified, tests added, etc.}
@@ -132,18 +132,18 @@ Deliverables:
 - [ ] Verified all workflow steps are complete
 - [ ] Updated task.md with completed status and timestamp
 - [ ] Moved task directory to `.agents/workspace/completed/`
-- [ ] Verified archive succeeded
+- [ ] Verified move succeeded
 - [ ] Informed user of completion
 
 ## Notes
 
-1. **Premature completion**: Do not archive a task that has incomplete steps. Examples of incomplete situations:
+1. **Premature completion**: Do not move a task that has incomplete steps. Examples of incomplete situations:
    - Code is written but not committed
    - Code is committed but not reviewed
    - Review found blockers that haven't been fixed
    - PR is created but not merged
 
-2. **Rollback**: If a task was archived incorrectly:
+2. **Rollback**: If a task was incorrectly moved:
    ```bash
    mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
    ```