Best fit
- 通过分类问题和拉取请求、关联活跃工作、保持GitHub对外可见而Linear作为内部执行层，来协调GitHub和Linear之间的执行流程。当用户需要待办事项控制、PR分类或GitHub与Linear协调时使用。
affaan-m/ECC
project-flow-ops
通过分类问题和拉取请求、关联活跃工作、保持GitHub对外可见而Linear作为内部执行层，来协调GitHub和Linear之间的执行流程。当用户需要待办事项控制、PR分类或GitHub与Linear协调时使用。
55Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/project-flow-ops"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn project-flow-ops's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 此技能将分散的 GitHub Issue、PR 和 Linear 任务整合为一条执行流程。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/project-flow-ops"Bring this context
- A concrete task that matches the documented purpose of project-flow-ops.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned project-flow-ops instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read project-flow-ops through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
使用时机
梳理开放的 PR 或 Issue 积压 决定哪些应放入 Linear，哪些应保留在 GitHub 中 将活跃的 GitHub 工作与内部执行通道关联 将 PR 分类为：合并、移植/重建、关闭或搁置 审查评论、CI 失败或过时 Issue 是否阻碍执行
梳理开放的 PR 或 Issue 积压决定哪些应放入 Linear，哪些应保留在 GitHub 中将活跃的 GitHub 工作与内部执行通道关联
运营模式
GitHub 是公开和社区的真实来源 Linear 是内部执行的真实来源，用于活跃的已排期工作 并非每个 GitHub Issue 都需要创建 Linear Issue 仅当工作满足以下条件时，才创建或更新 Linear： 活跃 已委派 已排期 跨职能 重要到需要内部跟踪
GitHub 是公开和社区的真实来源Linear 是内部执行的真实来源，用于活跃的已排期工作并非每个 GitHub Issue 都需要创建 Linear Issue
核心工作流
GitHub Issue 或 PR 状态 作者和分支状态 审查评论 CI 状态 关联的 Issue
GitHub Issue 或 PR 状态作者和分支状态审查评论
1. 首先阅读公开信息
GitHub Issue 或 PR 状态 作者和分支状态 审查评论 CI 状态 关联的 Issue
GitHub Issue 或 PR 状态作者和分支状态审查评论
2. 对工作进行分类
Review the “2. 对工作进行分类” section in the pinned source before continuing.
Review and apply the “2. 对工作进行分类” source section.
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use project-flow-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned project-flow-ops source to [task]. Pay particular attention to these source sections: “使用时机”, “运营模式”, “核心工作流”, “1. 首先阅读公开信息”, “2. 对工作进行分类”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current project-flow-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “使用时机” has been checked.
The source section “运营模式” has been checked.
The source section “核心工作流” has been checked.
The source section “1. 首先阅读公开信息” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailproject-flow-ops
日本語翻訳：このファイルは project-flow-ops 用の日本語翻訳が必要です
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does project-flow-ops do?
此技能将分散的 GitHub Issue、PR 和 Linear 任务整合为一条执行流程。
How do I start using project-flow-ops?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/project-flow-ops". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
55/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation16/30
Specificity7/25
Maintenance20/20
Trust signals12/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
project-flow-ops by affaan-m
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
project-flow-ops by affaan-m
日本語翻訳：このファイルは project-flow-ops 用の日本語翻訳が必要です
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
项目流程运营
此技能将分散的 GitHub Issue、PR 和 Linear 任务整合为一条执行流程。
当问题在于协调而非编码时使用。
使用时机
- 梳理开放的 PR 或 Issue 积压
- 决定哪些应放入 Linear，哪些应保留在 GitHub 中
- 将活跃的 GitHub 工作与内部执行通道关联
- 将 PR 分类为：合并、移植/重建、关闭或搁置
- 审查评论、CI 失败或过时 Issue 是否阻碍执行
运营模式
- GitHub 是公开和社区的真实来源
- Linear 是内部执行的真实来源，用于活跃的已排期工作
- 并非每个 GitHub Issue 都需要创建 Linear Issue
- 仅当工作满足以下条件时，才创建或更新 Linear：
- 活跃
- 已委派
- 已排期
- 跨职能
- 重要到需要内部跟踪
核心工作流
1. 首先阅读公开信息
收集：
- GitHub Issue 或 PR 状态
- 作者和分支状态
- 审查评论
- CI 状态
- 关联的 Issue
2. 对工作进行分类
每个项目应归入以下状态之一：
| 状态 | 含义 |
|---|---|
| 合并 | 独立完整、符合策略、准备就绪 |
| 移植/重建 | 有用的想法，但应在 ECC 内部手动重新落地 |
| 关闭 | 方向错误、过时、不安全或重复 |
| 搁置 | 可能有用，但当前未排期 |
3. 判断是否需要 Linear
仅在以下情况下创建或更新 Linear：
- 执行正在积极规划中
- 涉及多个仓库或工作流
- 工作需要内部所有权或排序
- 该 Issue 是更大项目通道的一部分
不要机械地镜像所有内容。
4. 保持两个系统一致
当工作活跃时：
- GitHub Issue/PR 应说明公开进展
- Linear 应在内部跟踪负责人、优先级和执行通道
当工作完成或被拒绝时：
- 将公开解决方案发布回 GitHub
- 相应地标记 Linear 任务
审查规则
- 切勿仅凭标题、摘要或信任进行合并；需使用完整差异
- 当外部来源的功能有价值但不独立完整时，应在 ECC 内部重建
- CI 红色表示需分类并修复或阻止；不要假装其已可合并
- 如果真正的阻碍是产品方向，请直接说明，而非隐藏在工具背后
输出格式
返回：
公开状态
- 议题 / 拉取请求状态
- 持续集成 / 审查状态
分类
- 合并 / 移植重建 / 关闭 / 搁置
- 一段理由说明
线性操作
- 创建 / 更新 / 无需线性项
- 项目 / 泳道（如适用）
下一步操作者行动
- 确切的下一个步骤
良好用例
- "审查开放的 PR 积压，告诉我哪些应合并，哪些应重建"
- "将 GitHub Issue 映射到我们的 ECC 1.x 和 ECC 2.0 项目通道"
- "检查这是否需要创建 Linear Issue，还是应保留在 GitHub 中"
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/project-flow-ops/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected