Project Flow Ops

This is triage infrastructure for teams running public GitHub repos with private Linear execution. It reads PR and issue state, classifies each item as merge, port/rebuild, close, or park, then decides whether Linear tracking is warranted or if it should stay GitHub-only. The core insight is that not everything public needs to be mirrored internally. You'd use this when backlog sprawl is hiding the actual execution lane, or when you need to audit what's ready to ship versus what needs to be rebuilt in-house. It won't merge anything without reading the full diff, and it treats CI failures and product direction blocks as first-class signals, not noise to route around.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill project-flow-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

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

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