Project Flow Ops

This is for teams running dual systems where GitHub faces the public and Linear tracks internal execution. It triages open PRs and issues into merge, port/rebuild, close, or park, then decides whether each item warrants a Linear task based on whether it's actually scheduled, delegated, or cross-functional. The workflow prevents mechanical mirroring of everything into Linear while keeping the two systems consistent when work is genuinely active. Useful when your backlog is a mix of community contributions, stale issues, and real execution work that needs sorting. The classification framework is straightforward and the anti-pattern it solves is real: not every public issue belongs in your internal tracker.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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