specline 2.0.0 → 2.0.2

package/templates/.cursor/hooks/specline-reminder.sh

@@ -1,147 +0,0 @@
-#!/usr/bin/env bash
-# specline-reminder.sh — postToolUse Hook
-# 关键操作后注入下一步提醒到 Agent 上下文
-#
-# Input (stdin JSON):
-#   { "tool_name": "Task"|"Write"|..., "tool_input": {...}, "tool_output": "...", ... }
-#
-# Output (stdout JSON):
-#   { "additional_context": "<提醒文本>" }  或  {}
-
-set -euo pipefail
-
-input=$(cat)
-tool_name=$(echo "$input" | jq -r '.tool_name // empty')
-tool_input=$(echo "$input" | jq -r '.tool_input // "{}"')
-SESSION_ID=$(echo "$input" | jq -r '.session_id // empty')
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
-CHANGES_DIR="$PROJECT_ROOT/specline/changes"
-
-# ===== 辅助函数 =====
-
-resolve_pipeline_for_session() {
-  local session_id="$1"
-  local bindings_file="$PROJECT_ROOT/specline/.pipeline-sessions.json"
-
-  if [ ! -f "$bindings_file" ]; then
-    return 1
-  fi
-
-  local change_name
-  change_name=$(jq -r --arg sid "$session_id" '.[$sid].change // empty' "$bindings_file" 2>/dev/null)
-
-  if [ -z "$change_name" ]; then
-    return 1
-  fi
-
-  local state_file="$CHANGES_DIR/$change_name/.pipeline-state.json"
-
-  if [ ! -f "$state_file" ]; then
-    # 脏数据：绑定存在但 pipeline 已不存在，清理绑定
-    jq --arg sid "$session_id" 'del(.[$sid])' "$bindings_file" > "$bindings_file.tmp" && mv "$bindings_file.tmp" "$bindings_file"
-    return 1
-  fi
-
-  STATE_FILE="$state_file"
-  return 0
-}
-
-STATE_FILE=""
-if ! resolve_pipeline_for_session "$SESSION_ID"; then
-  echo '{}'
-  exit 0
-fi
-
-phase=$(jq -r '.current_phase' "$STATE_FILE")
-change=$(jq -r '.change_name' "$STATE_FILE")
-
-# ---- Task (子Agent) 完成后 ----
-if [ "$tool_name" = "Task" ]; then
-  subagent_type=$(echo "$tool_input" | jq -r '.subagent_type // ""')
-
-  if [ "$phase" = "coding" ] && echo "$subagent_type" | grep -qE "^specline-"; then
-    # 检查是否还有同批次未完成的任务
-    pending_in_batch="?"
-    pending_tasks=$(jq -r '[.phases.coding.tasks[]? | select(.status == "pending")] | length' "$STATE_FILE" 2>/dev/null || echo "0")
-
-    reminder="🔔 **[Pipeline] 子 Agent ($subagent_type) 已完成**\n"
-    reminder+="- 变更: $change | 阶段: CODING\n"
-
-    if [ "$pending_tasks" != "0" ] && [ "$pending_tasks" != "?" ]; then
-      reminder+="- 还有 ${pending_tasks} 个任务未完成\n"
-    fi
-
-    reminder+="- ⚠️ 请更新 tasks.md 中对应任务的 checkbox：[ ] → [x]\n"
-    reminder+="- ⚠️ 当前批次全部完成后，运行 Build Gate:\n"
-    reminder+="  \`.cursor/hooks/specline-pipeline-gate.sh build --change \"$change\"\`"
-
-    escaped=$(echo -e "$reminder" | jq -Rs '.')
-    cat << EOF
-{
-  "additional_context": ${escaped}
-}
-EOF
-    exit 0
-  fi
-
-  if [ "$phase" = "test" ] && echo "$subagent_type" | grep -qE "^specline-"; then
-    reminder="🔔 **[Pipeline] 测试修复 Agent ($subagent_type) 已完成**\n"
-    reminder+="- 变更: $change | 阶段: TEST\n"
-    reminder+="- ⚠️ 请重新运行对应的测试 Gate:\n"
-    reminder+="  \`.cursor/hooks/specline-pipeline-gate.sh test-unit --change \"$change\"\`"
-
-    escaped=$(echo -e "$reminder" | jq -Rs '.')
-    cat << EOF
-{
-  "additional_context": ${escaped}
-}
-EOF
-    exit 0
-  fi
-fi
-
-# ---- Write / StrReplace 完成后 ----
-if [ "$tool_name" = "Write" ] || [ "$tool_name" = "StrReplace" ]; then
-  file_path=$(echo "$tool_input" | jq -r '.path // .file_path // empty')
-
-  if [ "$phase" = "coding" ] && [ -n "$file_path" ]; then
-    # 编辑 tasks.md → 不提醒（这是正确的行为）
-    if echo "$file_path" | grep -q "tasks.md"; then
-      echo '{}'
-      exit 0
-    fi
-
-    # 编辑代码文件 → 提醒（Orchestrator 不应该直接编辑）
-    if echo "$file_path" | grep -qE '\.(ts|tsx|js|jsx|py|go|rs)$'; then
-      reminder="🔔 **[Pipeline] 检测到直接编辑代码文件**\n"
-      reminder+="- 文件: $(basename "$file_path")\n"
-      reminder+="- 编码应通过子 Agent 完成，而非直接编辑\n"
-      reminder+="- 如果这是 Orchestrator 的错误行为，请改用 Task 工具启动对应子 Agent"
-
-      escaped=$(echo -e "$reminder" | jq -Rs '.')
-      cat << EOF
-{
-  "additional_context": ${escaped}
-}
-EOF
-      exit 0
-    fi
-  fi
-fi
-
-# ---- Shell 执行后检查 Gate ----
-if [ "$tool_name" = "Shell" ]; then
-  command=$(echo "$tool_input" | jq -r '.command // empty')
-
-  # 如果是执行 gate 脚本 → 不提醒
-  if echo "$command" | grep -q "specline-pipeline-gate.sh"; then
-    echo '{}'
-    exit 0
-  fi
-fi
-
-# 默认：无提醒
-echo '{}'
-exit 0

package/templates/.cursor/hooks/specline-session-start.sh

@@ -1,259 +0,0 @@
-#!/usr/bin/env bash
-# specline-session-start.sh — sessionStart Hook (Pipeline Session Binding)
-#
-# 新会话启动时:
-#   1. 清理过期绑定（7 天未更新）
-#   2. 检查当前 session 是否已有绑定
-#   3. 有绑定且 pipeline 仍活跃 → 使用已有绑定，注入上下文
-#   4. 有绑定但 pipeline 已失效 → 清理脏数据，重新扫描
-#   5. 无绑定 → 透明放行（echo '{}'）——不自动绑定，避免跨窗口污染
-#
-# Input (stdin JSON):
-#   { "session_id": "...", "is_background_agent": bool, ... }
-#
-# Output (stdout JSON):
-#   { "additional_context": "<pipeline 上下文>" }  或  {}（无活跃 pipeline）
-
-set -euo pipefail
-
-# ============================================================================
-# Input
-# ============================================================================
-
-input=$(cat)
-
-# 跳过 background agent（子 Agent 不需要 pipeline 上下文）
-is_bg=$(echo "$input" | jq -r '.is_background_agent // false')
-if [ "$is_bg" = "true" ]; then
-  echo '{}'
-  exit 0
-fi
-
-session_id=$(echo "$input" | jq -r '.session_id // empty')
-if [ -z "$session_id" ]; then
-  echo '{}'
-  exit 0
-fi
-
-# ============================================================================
-# Paths
-# ============================================================================
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
-BINDINGS_FILE="$PROJECT_ROOT/specline/.pipeline-sessions.json"
-CHANGES_DIR="$PROJECT_ROOT/specline/changes"
-
-# ============================================================================
-# Helper Functions
-# ============================================================================
-
-# init_bindings_file — ensure bindings file exists with a valid JSON object
-init_bindings_file() {
-  if [ ! -f "$BINDINGS_FILE" ]; then
-    mkdir -p "$(dirname "$BINDINGS_FILE")"
-    echo '{}' > "$BINDINGS_FILE"
-  fi
-
-  # Validate it's readable JSON; reset if corrupted
-  if ! jq empty "$BINDINGS_FILE" 2>/dev/null; then
-    echo '{}' > "$BINDINGS_FILE"
-  fi
-}
-
-# clean_expired_bindings — remove bindings where bound_at > 7 days ago
-# Uses ISO-8601 lexical comparison: works on both macOS and Linux
-clean_expired_bindings() {
-  [ -f "$BINDINGS_FILE" ] || return 0
-
-  local cutoff_date
-  # macOS date, fallback to Linux date
-  cutoff_date=$(date -u -v-7d +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || \
-                date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null)
-
-  if [ -z "$cutoff_date" ]; then
-    return 0  # Cannot determine cutoff, skip cleanup
-  fi
-
-  local tmp_file="${BINDINGS_FILE}.tmp"
-  # Keep only entries whose bound_at is >= cutoff (i.e. within the last 7 days)
-  jq --arg cutoff "$cutoff_date" \
-    'with_entries(select(.value.bound_at >= $cutoff))' \
-    "$BINDINGS_FILE" > "$tmp_file" 2>/dev/null && \
-    mv "$tmp_file" "$BINDINGS_FILE" 2>/dev/null || true
-}
-
-# is_pipeline_active — check if a pipeline's state file exists and is not archived
-# Returns 0 (active) or 1 (inactive)
-is_pipeline_active() {
-  local change_name="$1"
-  local state_file="$CHANGES_DIR/$change_name/.pipeline-state.json"
-
-  [ -f "$state_file" ] || return 1
-
-  local phase
-  phase=$(jq -r '.current_phase // "unknown"' "$state_file" 2>/dev/null)
-  [ "$phase" != "archive" ] || return 1
-
-  return 0
-}
-
-# scan_active_pipelines — scan changes/ (excluding archive/) for active pipelines
-# Output: one line per pipeline: change_name|phase|state_file_path
-scan_active_pipelines() {
-  if [ ! -d "$CHANGES_DIR" ]; then
-    return 0
-  fi
-
-  for state_file in "$CHANGES_DIR"/*/.pipeline-state.json; do
-    [ -f "$state_file" ] || continue
-
-    # Exclude archive/
-    case "$state_file" in
-      */archive/*) continue ;;
-    esac
-
-    local change_name phase
-    change_name=$(jq -r '.change_name // ""' "$state_file" 2>/dev/null)
-    phase=$(jq -r '.current_phase // ""' "$state_file" 2>/dev/null)
-
-    [ -n "$change_name" ] || continue
-    [ "$phase" != "archive" ] || continue
-
-    printf '%s|%s|%s\n' "$change_name" "$phase" "$state_file"
-  done
-}
-
-# phase_constraints — output constraint text for a given phase (to stdout)
-phase_constraints() {
-  local phase="$1"
-  case "$phase" in
-    spec)
-      printf '%s\n' "- 只能通过 specline-spec-creator / specline-spec-reviewer 子 Agent 工作"
-      printf '%s\n' "- 禁止编辑任何应用代码文件（.ts/.tsx/.py/.go 等）"
-      printf '%s\n' "- 规划文件生成后需运行 Spec Gate"
-      ;;
-    coding)
-      printf '%s\n' "- 编码必须通过子 Agent：specline-frontend-dev / specline-backend-dev / specline-config-dev"
-      printf '%s\n' "- 禁止直接编辑应用代码文件"
-      printf '%s\n' "- 每批次任务完成后运行 Build Gate"
-      printf '%s\n' "- 每个 Task 完成后更新 tasks.md 的 checkbox"
-      ;;
-    code_review)
-      printf '%s\n' "- 只能运行 specline-code-reviewer + Lint Gate"
-      printf '%s\n' "- 如需修复代码，通过子 Agent 完成"
-      ;;
-    test)
-      printf '%s\n' "- 运行测试 Gate 链：unit → integration → e2e"
-      printf '%s\n' "- 测试失败时通过 specline-test-runner 分析原因"
-      printf '%s\n' "- 代码修复通过子 Agent，测试修复通过 specline-test-writer"
-      ;;
-    *)
-      printf '%s\n' "- 遵循 specline-pipeline SKILL 的当前阶段约束"
-      ;;
-  esac
-}
-
-# build_context — generate a JSON-escaped additional_context string for a bound pipeline
-build_context() {
-  local change_name="$1"
-  local phase="$2"
-  local state_file="$3"
-
-  {
-    printf '🚨 **Specline Pipeline 运行中**\n\n'
-    printf '**当前变更**: %s\n' "$change_name"
-    printf '**当前阶段**: %s\n' "$phase"
-
-    # Task progress for coding phase
-    if [ "$phase" = "coding" ] && [ -f "$state_file" ]; then
-      local completed total
-      completed=$(jq -r '[.phases.coding.tasks[]? | select(.status == "completed")] | length' "$state_file" 2>/dev/null || printf '0')
-      total=$(jq -r '[.phases.coding.tasks[]?] | length' "$state_file" 2>/dev/null || printf '0')
-      if [ "$total" != "0" ]; then
-        printf '**任务进度**: %s/%s 完成\n' "$completed" "$total"
-      fi
-    fi
-
-    printf '\n**阶段约束**:\n'
-    phase_constraints "$phase"
-    printf '\n'
-    printf '**重要**: 你是 Specline Pipeline 编排者。上述约束具有最高优先级，必须在每个操作前检查是否符合当前阶段要求。'
-  } | jq -Rs '.'
-}
-
-# phase_constraint_table — static phase constraint reference table (markdown)
-phase_constraint_table() {
-  cat << 'TABLEEOF'
-| 阶段 | 约束 |
-|------|------|
-| spec | 只能通过 specline-spec-creator/specline-spec-reviewer 子 Agent 工作，禁止编辑代码 |
-| coding | 必须通过子 Agent 编码，批次完成后运行 Build Gate，更新 tasks.md |
-| code_review | 只能运行 specline-code-reviewer + Lint Gate |
-| test | 运行测试 Gate 链：unit → integration → e2e |
-TABLEEOF
-}
-
-# write_binding — write a session_id → change_name binding to .pipeline-sessions.json
-write_binding() {
-  local sid="$1"
-  local change="$2"
-
-  local now_iso
-  now_iso=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-
-  local tmp_file="${BINDINGS_FILE}.tmp"
-  jq --arg sid "$sid" --arg change "$change" --arg now "$now_iso" \
-    '.[$sid] = {"change": $change, "bound_at": $now}' \
-    "$BINDINGS_FILE" > "$tmp_file" 2>/dev/null && \
-    mv "$tmp_file" "$BINDINGS_FILE" 2>/dev/null || true
-}
-
-# delete_binding — remove a session_id entry from .pipeline-sessions.json
-delete_binding() {
-  local session_id="$1"
-
-  [ -f "$BINDINGS_FILE" ] || return 0
-
-  local tmp_file="${BINDINGS_FILE}.tmp"
-  jq --arg sid "$session_id" 'del(.[$sid])' "$BINDINGS_FILE" > "$tmp_file" 2>/dev/null && \
-    mv "$tmp_file" "$BINDINGS_FILE" 2>/dev/null || true
-}
-
-# ============================================================================
-# Main Logic
-# ============================================================================
-
-init_bindings_file
-
-# 1. Clean expired bindings (bound_at > 7 days ago)
-clean_expired_bindings
-
-# 2. Check existing binding for this session
-existing_change=""
-if [ -f "$BINDINGS_FILE" ]; then
-  existing_change=$(jq -r --arg sid "$session_id" '.[$sid].change // empty' "$BINDINGS_FILE" 2>/dev/null)
-fi
-
-if [ -n "$existing_change" ]; then
-  if is_pipeline_active "$existing_change"; then
-    # Binding is still valid — use it
-    state_file="$CHANGES_DIR/$existing_change/.pipeline-state.json"
-    phase=$(jq -r '.current_phase // "unknown"' "$state_file" 2>/dev/null)
-
-    ctx_json=$(build_context "$existing_change" "$phase" "$state_file")
-
-    printf '{\n  "additional_context": %s\n}\n' "$ctx_json"
-    exit 0
-  else
-    # Dirty data: pipeline archived or deleted — clean up and rescan
-    delete_binding "$session_id"
-  fi
-fi
-
-
-# 3. No (valid) binding → transparent pass-through
-# 不再自动绑定或注入任何 pipeline 上下文，避免跨窗口污染。
-# 用户需通过 /specline-pipeline --change <name> 显式绑定。
-echo '{}'
-exit 0

package/templates/.cursor/hooks/specline-shell-guard.sh

@@ -1,18 +0,0 @@
-#!/usr/bin/env bash
-# shell-guard.sh — beforeShellExecution Hook: 拦截危险命令
-input=$(cat)
-command=$(echo "$input" | jq -r '.command // empty')
-if echo "$command" | grep -qE "rm -rf|rm -r "; then
-  echo '{"permission": "deny", "user_message": "危险命令被拦截: rm -rf"}'
-  exit 0
-fi
-if echo "$command" | grep -qE "curl.*\|.*bash|wget.*\|.*sh"; then
-  echo '{"permission": "deny", "user_message": "危险命令被拦截: 管道执行远程脚本"}'
-  exit 0
-fi
-if echo "$command" | grep -qE "^sudo "; then
-  echo '{"permission": "deny", "user_message": "sudo 需要人工审批"}'
-  exit 0
-fi
-echo '{"permission": "allow"}'
-exit 0

package/templates/.cursor/hooks.json

@@ -1,46 +0,0 @@
-{
-  "version": 1,
-  "hooks": {
-    "sessionStart": [
-      {
-        "command": ".cursor/hooks/specline-session-start.sh",
-        "timeout": 10
-      }
-    ],
-    "preToolUse": [
-      {
-        "command": ".cursor/hooks/specline-phase-guard.sh",
-        "matcher": "Write|StrReplace|EditNotebook|Task|Delete",
-        "timeout": 5,
-        "failClosed": false
-      }
-    ],
-    "postToolUse": [
-      {
-        "command": ".cursor/hooks/specline-reminder.sh",
-        "matcher": "Task|Write|StrReplace|Shell",
-        "timeout": 5
-      }
-    ],
-    "subagentStart": [
-      {
-        "command": ".cursor/hooks/specline-agent-guard.sh",
-        "matcher": "specline-spec-creator|specline-spec-reviewer|specline-frontend-dev|specline-backend-dev|specline-config-dev|specline-code-reviewer|specline-config-reviewer|specline-test-writer|specline-test-runner",
-        "failClosed": true
-      }
-    ],
-    "beforeShellExecution": [
-      {
-        "command": ".cursor/hooks/specline-shell-guard.sh",
-        "matcher": "rm -rf|curl.*\\|.*bash|wget.*\\|.*sh|^sudo ",
-        "failClosed": true
-      }
-    ],
-    "afterFileEdit": [
-      {
-        "command": ".cursor/hooks/specline-auto-format.sh",
-        "matcher": "\\.(py|ts|tsx|js)$"
-      }
-    ]
-  }
-}

package/templates/.cursor/skills/specline-apply-change/SKILL.md

@@ -1,197 +0,0 @@
----
-name: specline-apply-change
-description: Implement tasks from a Specline change. Use when the user wants to start implementing, continue implementation, or work through tasks.
-license: MIT
-compatibility: Compatible with specline.
-metadata:
-  author: specline
-  version: "1.0"
-  generatedBy: "1.3.1"
----
-
-Implement tasks from a Specline change.
-
-**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
-
-## 速览 (Layer 1)
-
-> **一句话**：实现 Specline change 中的编码任务。
-> **入口**：`/specline-apply-change [change-name]` 或直接说「继续实现」
-> **流程**：选 change → 读上下文 → 逐任务实现 → 标记完成
-
-> ⚠️ **人机门禁策略感知**：当调用方传递了 `HUMAN_GATE_POLICY=minimal` 或 `HUMAN_GATE_POLICY=none` 上下文时，本 Skill 内所有的 `AskUserQuestion` 交互应自动采用默认安全选项：
-> - change 选择 → 若上下文中已有 change name，直接使用；否则取第一个活跃 change
-> - 其他确认交互 → 自动采用默认安全选项继续，不暂停等待人工输入
-
-**Fluid Workflow Integration**
-
-This skill supports the "actions on a change" model:
-- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
-- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
-
-**开始前请确认：**
-- [ ] Change 已选中（`/specline-pipeline --change <name>`）
-- [ ] 已读取 proposal.md（知道做什么）
-- [ ] 已读取 spec.md（知道需求和场景）
-- [ ] 已读取 design.md（知道技术决策）
-- [ ] 已读取 tasks.md（知道实现清单）
-
-## 详细步骤 — Happy Path (Layer 2)
-
-**Steps**
-
-1. **Select the change**
-
-   If a name is provided, use it. Otherwise:
-   - Infer from conversation context if the user mentioned a change
-   - Auto-select if only one active change exists
-   - If ambiguous, run `specline-pipeline-gate.sh list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
-
-   Always announce: "Using change: <name>" and how to override (e.g., `/specline-pipeline --change <other>`).
-
-2. **Check status to understand the schema**
-   ```bash
-   specline-pipeline-gate.sh artifacts --change "<name>" --json
-   ```
-   Parse the JSON to understand:
-   - `schemaName`: The workflow being used (e.g., "spec-driven")
-   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
-
-3. **Read context files**
-
-   Read the planning files at `specline/changes/<name>/`:
-   - `proposal.md` — what & why
-   - `specs/<capability>/spec.md` — requirements & scenarios
-   - `design.md` — architecture & decisions
-   - `tasks.md` — implementation checklist
-
-   Check task completion: count `- [ ]` (incomplete) vs `- [x]` (complete).
-
-4. **Show current progress**
-
-   Display:
-   - Progress: "N/M tasks complete"
-   - Remaining tasks overview
-
-5. **Implement tasks (loop until done or blocked)**
-
-   For each pending task:
-   - Show which task is being worked on
-   - Make the code changes required
-   - Keep changes minimal and focused
-   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
-   - Continue to next task
-
-   **Pause if:**
-   - Task is unclear → ask for clarification
-   - Implementation reveals a design issue → suggest updating artifacts
-   - Error or blocker encountered → report and wait for guidance
-   - User interrupts
-
-6. **On completion or pause, show status**
-
-   Display:
-   - Tasks completed this session
-   - Overall progress: "N/M tasks complete"
-   - If all done: suggest archive
-   - If paused: explain why and wait for guidance
-
-## 输出模板 & 高级话题 (Layer 3)
-
-### 输出模板
-
-**Output During Implementation**
-
-```
-## Implementing: <change-name> (schema: <schema-name>)
-
-Working on task 3/7: <task description>
-[...implementation happening...]
-✓ Task complete
-
-Working on task 4/7: <task description>
-[...implementation happening...]
-✓ Task complete
-```
-
-**Output On Completion**
-
-```
-## Implementation Complete
-
-**Change:** <change-name>
-**Schema:** <schema-name>
-**Progress:** 7/7 tasks complete ✓
-
-### Completed This Session
-- [x] Task 1
-- [x] Task 2
-...
-
-All tasks complete! Ready to archive this change.
-```
-
-**Output On Pause (Issue Encountered)**
-
-```
-## Implementation Paused
-
-**Change:** <change-name>
-**Schema:** <schema-name>
-**Progress:** 4/7 tasks complete
-
-### Issue Encountered
-<description of the issue>
-
-**Options:**
-1. <option 1>
-2. <option 2>
-3. Other approach
-
-What would you like to do?
-```
-
-### Guardrails
-- Keep going through tasks until done or blocked
-- Always read context files before starting (from the apply instructions output)
-- If task is ambiguous, pause and ask before implementing
-- If implementation reveals issues, pause and suggest artifact updates
-- Keep code changes minimal and scoped to each task
-- Update task checkbox immediately after completing each task
-- Pause on errors, blockers, or unclear requirements - don't guess
-- Use contextFiles from CLI output, don't assume specific file names
-- **Hook blocked → no silent fallback**: If this skill is invoked because a coding subagent (specline-frontend-dev / specline-backend-dev) was blocked by a hook, you MUST first notify the user of the blocking cause and attempt diagnosis. Do not silently execute tasks that should have been handled by the blocked subagent. Reference the Hook Blocking Resolution Protocol in the specline-pipeline skill.
-
----
-
-## Anti-Rationalization 表格
-
-逐任务实现时，Agent 容易偏离规范：
-
-| 借口 | 现实 |
-|------|------|
-| "不用读 Spec/Design/Tasks，我理解需求" | 记忆不可靠。实现前读上下文文件是防止方向偏离的最便宜保险。 |
-| "顺便把这个相邻函数也重构了" | Scope Discipline 是 Core Behaviors。越界修改让 Code Review 和回溯都变困难。 |
-| "checkbox 我最后一起标记" | Checkbox 是断点续跑的唯一信号源。不及时标记意味着下次恢复时状态丢失。 |
-| "这个任务没有测试也没关系，下一个任务会补" | 每个 Testable=true 的任务必须产出测试。推迟 = 不写。 |
-| "tasks.md 的 Covers 追溯链我不用管，代码写对就行" | Covers 链是 Spec → Code 的可追溯纽带。不维护它，Code Review 和测试失败定位都失去锚点。 |
-
-## Verification Checklist
-
-每完成一个任务后自查，全部完成后终查：
-
-- [ ] 开始前已读 proposal.md / spec.md / design.md / tasks.md
-- [ ] 每个任务的实现范围未超出 Files 声明
-- [ ] 每个 Testable=true 的任务产出了测试文件（在 tests/unit/ 或 tests/models/）
-- [ ] tasks.md 中每个已完成任务的 `[ ]` 已改为 `[x]`
-- [ ] task-{id}-result.json 已写入 .tmp/ 目录
-- [ ] 本 session 修改的文件与 tasks.md 的 Files 声明一致
-- [ ] 未修改其他任务负责的文件
-
-### 暂停场景处理
-
-当实现过程中出现以下情况时，暂停并等待用户指引：
-- 任务描述不清晰 → 请求用户澄清
-- 实现中暴露出设计问题 → 建议更新 Artifact（proposal / spec / design / tasks）
-- 遇到错误或阻塞 → 报告具体问题并等待指导
-- 用户主动中断 → 记录当前进度，下次可从断点继续