Back to Details

project-flow-ops

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Project Flow Ops

项目流程运营

This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.
Use it when the problem is coordination, not coding.
该技能可将分散的GitHub issues、PRs和Linear任务整合为统一的执行流程。
适用于需要解决协同问题而非编码问题的场景。

When to Use

适用场景

  • Triage open PR or issue backlogs
  • Decide what belongs in Linear vs what should remain GitHub-only
  • Link active GitHub work to internal execution lanes
  • Classify PRs into merge, port/rebuild, close, or park
  • Audit whether review comments, CI failures, or stale issues are blocking execution
  • 分类处理待处理的PR或issue待办列表
  • 判定哪些事项应该进入Linear，哪些仅需保留在GitHub
  • 将正在进行的GitHub工作项关联到内部执行通道
  • 将PR分类为合并、移植/重构、关闭或搁置
  • 审核评审意见、CI运行失败或过时issue是否阻塞了执行流程

Operating Model

运营模式

  • GitHub is the public and community truth
  • Linear is the internal execution truth for active scheduled work
  • Not every GitHub issue needs a Linear issue
  • Create or update Linear only when the work is:
    • active
    • delegated
    • scheduled
    • cross-functional
    • important enough to track internally
  • GitHub是公开面向社区的事实数据源
  • Linear是已排期活跃工作的内部执行事实数据源
  • 并非所有GitHub issue都需要对应创建Linear issue
  • 仅当工作符合以下条件时，才需要创建或更新Linear事项：
    • 正在进行中
    • 已委派负责人
    • 已排期
    • 跨职能协作
    • 重要程度高，需要内部追踪

Core Workflow

核心工作流

1. Read the public surface first

1. 优先读取公开层面信息

Gather:
  • GitHub issue or PR state
  • author and branch status
  • review comments
  • CI status
  • linked issues
收集以下内容：
  • GitHub issue或PR状态
  • 作者和分支状态
  • 评审意见
  • CI状态
  • 关联的issues

2. Classify the work

2. 工作项分类

Every item should end up in one of these states:
StateMeaning
Mergeself-contained, policy-compliant, ready
Port/Rebuilduseful idea, but should be manually re-landed inside ECC
Closewrong direction, stale, unsafe, or duplicated
Parkpotentially useful, but not scheduled now
每个事项最终应归入以下状态之一：
状态含义
合并（Merge）功能独立、符合规范、已就绪
移植/重构（Port/Rebuild）想法有价值，但需要在ECC内部手动重新落地
关闭（Close）方向错误、过时、不安全或重复
搁置（Park）有潜在价值，但当前未排期

3. Decide whether Linear is warranted

3. 判定是否需要使用Linear

Create or update Linear only if:
  • execution is actively planned
  • multiple repos or workstreams are involved
  • the work needs internal ownership or sequencing
  • the issue is part of a larger program lane
Do not mirror everything mechanically.
仅当符合以下条件时，才需要创建或更新Linear事项：
  • 已明确规划要执行
  • 涉及多个代码仓库或工作流
  • 该工作需要内部负责人或排期序列
  • 该issue属于更大的项目通道的一部分
不要机械地同步所有内容。

4. Keep the two systems consistent

4. 保持两个系统数据一致

When work is active:
  • GitHub issue/PR should say what is happening publicly
  • Linear should track owner, priority, and execution lane internally
When work ships or is rejected:
  • post the public resolution back to GitHub
  • mark the Linear task accordingly
当工作正在进行时：
  • GitHub issue/PR应公开说明当前进展
  • Linear应在内部追踪负责人、优先级和执行通道
当工作已上线或被驳回时：
  • 将公开处理结果同步回GitHub
  • 对应标记Linear任务状态

Review Rules

评审规则

  • Never merge from title, summary, or trust alone; use the full diff
  • External-source features should be rebuilt inside ECC when they are valuable but not self-contained
  • CI red means classify and fix or block; do not pretend it is merge-ready
  • If the real blocker is product direction, say so instead of hiding behind tooling
  • 永远不要仅靠标题、摘要或信任就合并，必须查看完整diff
  • 外部贡献的功能如果有价值但不独立，需要在ECC内部重构
  • CI变红意味着需要分类处理并修复，或阻塞合并，不要假装它已经可以合并
  • 如果真正的阻塞因素是产品方向，要直接说明，不要拿工具当借口

Output Format

输出格式

Return:
text
PUBLIC STATUS
- issue / PR state
- CI / review state

CLASSIFICATION
- merge / port-rebuild / close / park
- one-paragraph rationale

LINEAR ACTION
- create / update / no Linear item needed
- project / lane if applicable

NEXT OPERATOR ACTION
- exact next move
返回以下内容：
text
PUBLIC STATUS
- issue / PR state
- CI / review state

CLASSIFICATION
- merge / port-rebuild / close / park
- one-paragraph rationale

LINEAR ACTION
- create / update / no Linear item needed
- project / lane if applicable

NEXT OPERATOR ACTION
- exact next move

Good Use Cases

优秀用例

  • "Audit the open PR backlog and tell me what to merge vs rebuild"
  • "Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes"
  • "Check whether this needs a Linear issue or should stay GitHub-only"
  • "审核待处理PR列表，告诉我哪些应该合并，哪些需要重构"
  • "将GitHub issues映射到我们的ECC 1.x和ECC 2.0项目通道中"
  • "检查这个事项是否需要创建Linear issue，还是仅保留在GitHub即可"