Project Flow Ops
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of project-flow-ops by affaan-m - installs and ranking accrue to the original listing.
project-flow-ops is a Claude Code skill that keeps GitHub as the public source of truth while using Linear only for active scheduled internal execution for developers who split public roadmap visibility from internal spr
About
project-flow-ops is an ECC skill that codifies a dual-track engineering workflow: GitHub remains the authoritative public record for issues, PRs, and roadmap visibility, while Linear holds only active, scheduled internal execution work. Teams adopt project-flow-ops to prevent duplicate ticket systems, reduce context switching, and keep external contributors aligned with GitHub while engineers run sprints and schedules in Linear. The published SKILL.md notes a Japanese translation in progress, but the described GitHub-plus-Linear operating model is the core deliverable. Engineering leads reach for project-flow-ops when scaling coordination across open-source visibility and private execution cadences.
- Triages open PR and issue backlogs automatically
- Classifies every PR into one of four states: merge, port/rebuild, close, or park
- Links active GitHub work to Linear only when the work is active, delegated, scheduled, cross-functional or high-priority
- Maintains GitHub as public/community truth and Linear as internal execution truth
- Audits review comments, CI failures, and stale items that block execution
Project Flow Ops by the numbers
- 1,367 all-time installs (skills.sh)
- +82 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill project-flow-opsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you sync GitHub and Linear without duplicate tickets?
Keep GitHub as the public source of truth while using Linear only for active, scheduled internal execution.
Who is it for?
Engineering teams using GitHub for public visibility and Linear for internal sprint execution who need a clear split of responsibilities.
Skip if: Solo repositories using only one issue tracker with no Linear instance should skip project-flow-ops.
When should I use this skill?
GitHub and Linear both hold issues and the team needs a single public source of truth plus scoped internal execution tracking.
What you get
Defined GitHub public source-of-truth rules, Linear active-work scope, and cross-tool execution workflow
- Workflow policy document
- Tool responsibility matrix
- Execution scheduling rules
Files
project-flow-ops - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は：D:/tmp/everything-claude-code/skills/project-flow-ops/SKILL.md
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Choose project-flow-ops when you need an explicit GitHub-versus-Linear responsibility split rather than mirroring every ticket in both systems.
FAQ
What is GitHub's role in project-flow-ops?
project-flow-ops designates GitHub as the public source of truth for issues, pull requests, and externally visible project status that contributors and stakeholders reference.
What does Linear handle in project-flow-ops?
project-flow-ops limits Linear to active, scheduled internal execution work so engineers run sprints and timelines without duplicating the public GitHub record.
When should teams adopt project-flow-ops?
project-flow-ops fits teams already using both GitHub and Linear who need clear boundaries between public roadmap visibility and private execution scheduling.