Linear任务自动更新技能：TDD工作流第7阶段追踪代理自动化工具

Update Linear Post-Job by auldsyababua/instructor-workflow

5 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/auldsyababua/instructor-workflow --skill 'Update Linear Post-Job'

项目管理自动化开发运维

🇨🇳中文介绍

更新 Linear 任务后处理

使用时机

在以下情况使用此技能：

任务完成时（追踪代理）：在 QA 验证实施且规划代理确认任务完成后
TDD 工作流的第 7 阶段：追踪代理处理 PR/文档和 Linear 更新
工作块追踪时：需要更新子任务状态并检查父任务完成情况

触发条件：

规划代理确认任务完成
QA 代理批准实施
PR 已合并，任务准备关闭
需要在 Linear 中追踪工作块进度

TDD 工作流上下文：

7 阶段 TDD：研究 → 规格说明 → Linear 丰富 → QA（测试）→ 行动（编码）→ QA（验证）→ 追踪（PR/文档）→ 仪表板更新
此技能：在第 7 阶段执行（追踪代理的职责）

工作流程

步骤 1：更新子任务状态

目的：在 Linear 中将已完成的任务（子任务）标记为“已完成”

前提条件：

规划代理已确认任务完成
QA 代理已批准实施
PR 已合并（如适用）
交接中包含子任务 ID

执行：

// 将子任务更新为“已完成”
await mcp__linear-server__update_issue({
  id: "LAW-5",  // 从交接中获取的子任务 ID
  state: "Done"
})

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 2：检查父工作块完成情况

目的：确定工作块中的所有子任务是否都已完成

// 1. 获取父任务详情
const parentIssue = await mcp__linear-server__get_issue({
  id: "LAW-4"  // 从交接中获取的父工作块 ID
})

// 2. 获取父任务的所有子任务
const childIssues = await mcp__linear-server__list_issues({
  team: "Linear-First-Agentic-Workflow",  // 来自 .project-context.md
  parentId: "LAW-4"  // 父工作块 ID
})

// 3. 检查是否所有子任务都已完成
const allChildrenDone = childIssues.nodes.every(
  issue => issue.state.name === "Done"
)

如果allChildrenDone === true：进行到步骤 3（更新父任务）
如果allChildrenDone === false：跳转到步骤 4（向规划代理报告）

需要检查的内容：

所有子任务必须满足 state.name === "Done"
检查所有同级任务（同一父任务下的其他子任务）
如果任何子任务仍处于“进行中”、“待办”或“已阻塞”状态，则不要更新父任务

步骤 3：更新父工作块（如果所有子任务都已完成）

目的：当所有子任务都完成时，将父工作块标记为“已完成”

仅在步骤 2 确定所有子任务都已完成时执行：

// 将父工作块更新为“已完成”
await mcp__linear-server__update_issue({
  id: "LAW-4",
  state: "Done"
})

// 向父任务添加完成评论
await mcp__linear-server__create_comment({
  issueId: "LAW-4",
  body: `✅ **工作块完成**

所有子任务已完成：
- LAW-5：研究代理升级 ✅
- LAW-6：规划代理重构 ✅
- LAW-7：追踪代理更新 ✅
[... 列出所有已完成的子任务 ...]

所有 PR 已合并。工作块准备关闭。`
})

父任务评论模板：

列出所有已完成的子任务
确认所有 PR 已合并
注明工作块准备关闭

如果父任务更新失败，向规划代理报告但不要阻塞：

try {
  await mcp__linear-server__update_issue({ id: "LAW-4", state: "Done" })
} catch (error) {
  // 向规划代理报告错误
  // 继续 - 即使父任务更新失败，任务仍然完成
}

步骤 4：向规划代理报告

目的：通知规划代理完成情况和任何问题

将完成报告写入交接位置（由规划代理指定）：

如果所有更新都成功：

**追踪代理完成报告**

✅ **所有 Linear 更新完成**

**子任务**：LAW-5 已更新为“已完成”
**父工作块**：LAW-4 [已更新为“已完成” | 仍有 N 个未完成的子任务]

**摘要**：
- PR #14 已成功合并
- Linear 任务已更新
- 工作块 [已完成 | 进行中]

[如果父任务完成] 根据第 7 阶段协议，主仪表板更新已委托给 Traycer。

准备接收下一个任务。

如果发生错误：

**追踪代理完成报告**

⚠️ **Linear 更新完成但存在错误**

**子任务**：LAW-5 - [成功更新 | 更新失败，需要手动干预]
**父工作块**：LAW-4 - [已检查，M 个子任务中有 N 个完成 | 检查失败]

**错误**：
- [列出遇到的任何错误]

**需要采取的行动**：
- [列出解决错误所需的手动步骤]

尽管 Linear 更新存在错误，但任务完成已确认。

重要：不要更新主仪表板 - 根据第 7 阶段协议，这由 Traycer 委托处理

场景：LAW-5（研究代理升级）完成，父任务是 LAW-4

// 步骤 1：更新子任务
await mcp__linear-server__update_issue({
  id: "LAW-5",
  state: "Done"
})

await mcp__linear-server__create_comment({
  issueId: "LAW-5",
  body: "✅ 任务完成。PR #14 已合并。"
})

// 步骤 2：检查父任务完成情况
const parentIssue = await mcp__linear-server__get_issue({ id: "LAW-4" })

const childIssues = await mcp__linear-server__list_issues({
  team: "Linear-First-Agentic-Workflow",
  parentId: "LAW-4"
})

const allDone = childIssues.nodes.every(i => i.state.name === "Done")

// 步骤 3：如果所有子任务都完成，则更新父任务
if (allDone) {
  // 所有 9 个子任务完成
  await mcp__linear-server__update_issue({
    id: "LAW-4",
    state: "Done"
  })

  await mcp__linear-server__create_comment({
    issueId: "LAW-4",
    body: "✅ 所有 9 个子任务完成。工作块完成。"
  })
}

// 步骤 4：向规划代理报告
// 将完成报告写入交接位置
// 不要更新主仪表板（由 Traycer 委托处理）

分支创建上下文

注意：此技能在分支创建和 PR 合并之后执行

7 阶段 TDD 工作流：

阶段 1：研究（尚未创建分支）
阶段 2：规格说明澄清（尚未创建分支）
阶段 3：Linear 丰富（尚未创建分支）
阶段 4 之前：创建分支
阶段 4-6：QA 创建测试 → 行动实施 → QA 验证（在分支上）
阶段 7：追踪代理处理 PR/文档和 Linear 更新 ← 此技能

分支命名约定（供参考）：

模式：feat/<父任务-id>-<子任务-id>-<简短描述>

# 工作块：LAW-4，子任务：LAW-5
feat/law-4-law-5-research-agent-upgrade

# 工作块：LAW-350，子任务：LAW-351
feat/law-350-law-351-webhook-server-setup

Linear MCP：mcp__linear-server__update_issue、mcp__linear-server__get_issue、mcp__linear-server__list_issues、mcp__linear-server__create_comment
项目上下文：.project-context.md（包含用于 Linear 查询的团队名称）
交接文件：规划代理提供子/父任务 ID

原始参考：post-job-linear-updates.md（已弃用 - 请改用此技能）
代理提示：
- 追踪代理：docs/agents/tracking/tracking-agent.md
- 规划代理：docs/agents/planning/planning-agent.md
相关参考文档：
- tdd-workflow-protocol.md - 完整的 7 阶段 TDD 工作流
- master-dashboard-creation-protocol.md - 仪表板更新协议（由 Traycer 委托处理）
- linear-update-protocol.md - 通用 Linear API 使用

条件	操作
子任务更新成功	继续检查父任务
子任务更新失败	添加错误评论，继续检查父任务
所有子任务已完成	将父任务更新为“已完成”，添加完成评论
部分子任务未完成	跳过父任务更新，向规划代理报告状态
父任务更新失败	报告错误，继续（不要因为父任务失败而阻塞）
所有更新完成	向规划代理报告成功

需要避免的常见陷阱

❌ 不要：直接更新主仪表板

原因：根据第 7 阶段协议，仪表板更新由 Traycer 委托处理
替代做法：向规划代理报告完成情况，让 Traycer 协调仪表板更新

❌ 不要：如果父任务更新失败则阻塞

原因：无论父任务状态如何，子任务都已完成
替代做法：向规划代理报告错误，将任务标记为完成

❌ 不要：不查询就假设所有子任务都已完成

原因：其他代理可能推迟了某个子任务
替代做法：始终查询所有子任务并检查状态

❌ 不要：将子任务状态更新为“已关闭”或“已取消”

原因：“已完成”是已完成任务的正确状态
替代做法：始终使用“已完成”状态

v1.0 (2025-11-05)：从 post-job-linear-updates.md 转换为技能格式
- 从参考文档中提取了 3 步工作流
- 添加了错误处理示例
- 明确了决策点和委托边界
- 包含了完整示例流程

🇺🇸English

Update Linear Post-Job

When to Use

Use this skill when:

Job completion (Tracking Agent): After QA validates implementation and Planning Agent confirms job complete
Phase 7 of TDD workflow : Tracking Agent handles PR/documentation and Linear updates
Work block tracking : Need to update child issue status and check parent completion

Triggers :

Planning Agent confirms job completion
QA Agent approves implementation
PR is merged and job is ready for closure
Need to track work block progress in Linear

TDD Workflow Context :

7-Phase TDD : Research → Spec → Linear Enrichment → QA (tests) → Action (code) → QA (validate) → Tracking (PR/docs) → Dashboard Update
This skill : Executes during Phase 7 (Tracking Agent responsibilities)

Workflow

Step 1: Update Child Issue Status

Purpose : Mark the completed job (child issue) as Done in Linear

Prerequisites :

Planning Agent confirmed job completion
QA Agent approved implementation
PR merged (if applicable)
Handoff includes child issue ID

Execute :

// Update child issue to Done
await mcp__linear-server__update_issue({
  id: "LAW-5",  // Child issue ID from handoff
  state: "Done"
})

Then add completion comment :

await mcp__linear-server__create_comment({
  issueId: "LAW-5",
  body: `✅ **Job Complete**

**PR**: #14 (https://github.com/org/repo/pull/14)
**QA Status**: ✅ All tests passing
**Files Changed**: 8 files, +420/-15 lines

Ready for merge.`
})

Comment Template Fields :

PR : Link to merged pull request (if applicable)
QA Status : Confirmation that QA validation passed
Files Changed : Summary of code changes
Additional Notes : Any relevant completion details

Error Handling :

If update fails, add comment instead and continue:

try {
  await mcp__linear-server__update_issue({ id: "LAW-5", state: "Done" })
} catch (error) {
  await mcp__linear-server__create_comment({
    issueId: "LAW-5",
    body: `⚠️ **Tracking Agent**: Could not update issue status to Done.

Error: ${error.message}

Job completion confirmed by Planning Agent. Manual status update needed.`
  })
  // Continue to Step 2 - don't block on child update failure
}

Step 2: Check Parent Work Block Completion

Purpose : Determine if all child jobs in the work block are complete

Execute :

// 1. Get parent issue details
const parentIssue = await mcp__linear-server__get_issue({
  id: "LAW-4"  // Parent work block ID from handoff
})

// 2. Get all child issues of parent
const childIssues = await mcp__linear-server__list_issues({
  team: "Linear-First-Agentic-Workflow",  // From .project-context.md
  parentId: "LAW-4"  // Parent work block ID
})

// 3. Check if ALL children are Done
const allChildrenDone = childIssues.nodes.every(
  issue => issue.state.name === "Done"
)

Decision Point :

IfallChildrenDone === true: Proceed to Step 3 (update parent)
IfallChildrenDone === false: Skip to Step 4 (report to Planning Agent)

What to check :

All child issues must have state.name === "Done"
Check all siblings (other child issues under same parent)
Do not update parent if any child is still In Progress, Todo, or Blocked

Step 3: Update Parent Work Block (If All Children Complete)

Purpose : Mark parent work block as Done when all child jobs complete

Execute only if Step 2 determined all children are Done :

// Update parent work block to Done
await mcp__linear-server__update_issue({
  id: "LAW-4",
  state: "Done"
})

// Add completion comment to parent
await mcp__linear-server__create_comment({
  issueId: "LAW-4",
  body: `✅ **Work Block Complete**

All child jobs completed:
- LAW-5: Research Agent Upgrade ✅
- LAW-6: Planning Agent Refactor ✅
- LAW-7: Tracking Agent Updates ✅
[... list all completed children ...]

All PRs merged. Work block ready for closure.`
})

Comment Template for Parent :

List all completed child jobs
Confirm all PRs merged
Note that work block is ready for closure

Error Handling :

If parent update fails, report to Planning Agent but don't block:

try {
  await mcp__linear-server__update_issue({ id: "LAW-4", state: "Done" })
} catch (error) {
  // Report error to Planning Agent
  // Continue - job is still complete even if parent update fails
}

Step 4: Report to Planning Agent

Purpose : Notify Planning Agent of completion and any issues

Write completion report to handoff location (specified by Planning Agent):

If all updates successful :

**Tracking Agent Completion Report**

✅ **All Linear Updates Complete**

**Child Issue**: LAW-5 updated to Done
**Parent Work Block**: LAW-4 [updated to Done | still has N incomplete children]

**Summary**:
- PR #14 merged successfully
- Linear issues updated
- Work block [complete | in progress]

[If parent complete] Master Dashboard update delegated to Traycer per Phase 7 protocol.

Ready for next job.

If errors occurred :

**Tracking Agent Completion Report**

⚠️ **Linear Updates Completed With Errors**

**Child Issue**: LAW-5 - [updated successfully | update failed, manual intervention needed]
**Parent Work Block**: LAW-4 - [checked, N of M children complete | check failed]

**Errors**:
- [List any errors encountered]

**Action Required**:
- [List manual steps needed to resolve errors]

Job completion confirmed despite Linear update errors.

Important : Do NOT update Master Dashboard - this is delegated by Traycer per Phase 7 protocol

Reference

Complete Example Flow

Scenario : LAW-5 (Research Agent Upgrade) complete, parent is LAW-4

// Step 1: Update child issue
await mcp__linear-server__update_issue({
  id: "LAW-5",
  state: "Done"
})

await mcp__linear-server__create_comment({
  issueId: "LAW-5",
  body: "✅ Job complete. PR #14 merged."
})

// Step 2: Check parent completion
const parentIssue = await mcp__linear-server__get_issue({ id: "LAW-4" })

const childIssues = await mcp__linear-server__list_issues({
  team: "Linear-First-Agentic-Workflow",
  parentId: "LAW-4"
})

const allDone = childIssues.nodes.every(i => i.state.name === "Done")

// Step 3: Update parent if all children complete
if (allDone) {
  // All 9 child jobs complete
  await mcp__linear-server__update_issue({
    id: "LAW-4",
    state: "Done"
  })

  await mcp__linear-server__create_comment({
    issueId: "LAW-4",
    body: "✅ All 9 child jobs complete. Work block done."
  })
}

// Step 4: Report to Planning Agent
// Write completion report to handoff location
// Do NOT update Master Dashboard (delegated by Traycer)

Branch Creation Context

Note : This skill executes AFTER branch creation and PR merge

7-Phase TDD Workflow :

Phase 1 : Research (no branch yet)
Phase 2 : Spec clarification (no branch yet)
Phase 3 : Linear Enrichment (no branch yet)
Just before Phase 4 : Create branch
Phase 4-6 : QA creates tests → Action implements → QA validates (on branch)
Phase 7 : Tracking Agent handles PR/docs and Linear updates ← This skill

Branch Naming Convention (for reference):

Pattern: feat/<parent-issue-id>-<child-issue-id>-<slug>

Examples:

# Work Block: LAW-4, Child Job: LAW-5
feat/law-4-law-5-research-agent-upgrade

# Work Block: LAW-350, Child Job: LAW-351
feat/law-350-law-351-webhook-server-setup

Related Tools

Linear MCP : mcp__linear-server__update_issue, mcp__linear-server__get_issue, mcp__linear-server__list_issues, mcp__linear-server__create_comment
Project Context : .project-context.md (contains team name for Linear queries)
Handoff Files : Planning Agent provides child/parent issue IDs

Decision Matrix

Condition	Action
Child update succeeds	Proceed to parent check
Child update fails	Add error comment, continue to parent check
All children Done	Update parent to Done, add completion comment
Some children incomplete	Skip parent update, report status to Planning Agent
Parent update fails	Report error, continue (don't block on parent failure)
All updates complete	Report success to Planning Agent

Common Pitfalls to Avoid

❌ Don't : Update Master Dashboard directly

Why : Dashboard updates are delegated by Traycer per Phase 7 protocol
Instead : Report completion to Planning Agent, let Traycer coordinate dashboard update

❌ Don't : Block if parent update fails

Why : Child job is complete regardless of parent status
Instead : Report error to Planning Agent, mark job as complete

❌ Don't : Assume all children Done without querying

Why : Another agent might have deferred a child job
Instead : Always query all child issues and check state

❌ Don't : Update child issue state to "Closed" or "Canceled"

Why : "Done" is the correct state for completed jobs
Instead : Always use "Done" state

Version History

v1.0 (2025-11-05): Converted from post-job-linear-updates.md to skill format
- Extracted 3-step workflow from reference doc
- Added error handling examples
- Clarified decision points and delegation boundaries
- Included complete example flow

Weekly Installs

Repository

auldsyababua/in…workflow

GitHub Stars

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

114,200 周安装