Agent skill

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.

MITAuto-check passedDevelopment

Install Project Flow Ops

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-flow-ops .claude/skills/project-flow-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .claude/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/project-flow-ops .agents/skills/project-flow-ops && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .agents/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/project-flow-ops .cursor/skills/project-flow-ops && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .cursor/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/affaan-m/ECC.git --path skills/project-flow-ops

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/project-flow-ops .gemini/skills/project-flow-ops && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .gemini/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/project-flow-ops .github/skills/project-flow-ops && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .github/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill project-flow-ops -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC project-flow-ops --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/project-flow-ops .opencode/skills/project-flow-ops && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "project-flow-ops" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/project-flow-ops into .opencode/skills/project-flow-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-flow-ops", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: project-flow-ops
GitHub stars: 277k
Used in: 3 other repos
Token cost: ~787 tokens
SKILL.md length: 372 words
Files: 1
Skills in repo: 683
Repo updated: Oct 11, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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.

Works in 4 steps: Read the public surface first → Classify the work → Decide whether Linear is warranted → …
The user wants backlog control
SKILL.md covers When to Use, Operating Model, Core Workflow and Review Rules, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Project Flow Ops is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

The user wants backlog control
GitHub-to-Linear coordination

Example prompts

“/project-flow-ops”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Read the public surface first
Classify the work
Decide whether Linear is warranted
Keep the two systems consistent

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Project Flow Ops loads about 787 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~73
When it runs · the whole SKILL.md, loaded when a task matches: ~787

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 372 words, ~787 tokens.

Download SKILL.mdSave it as .claude/skills/project-flow-ops/SKILL.md (or your agent's skills folder).

name: project-flow-ops
description: 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.
metadata.origin: ECC

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

Core Workflow

1. Read the public surface first

Gather:

GitHub issue or PR state
author and branch status
review comments
CI status
linked issues

2. Classify the work

Every item should end up in one of these states:

State	Meaning
Merge	self-contained, policy-compliant, ready
Port/Rebuild	useful idea, but should be manually re-landed inside ECC
Close	wrong direction, stale, unsafe, or duplicated
Park	potentially useful, but not scheduled now

3. Decide whether Linear is warranted

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.

Show full SKILL.md (143 more words)Show less

4. Keep the two systems consistent

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

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

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

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"

Files

Just SKILL.md in skills/project-flow-ops of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Project Flow Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Project Flow Ops compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Project Flow Ops this skillaffaan-m/ECC	277k	3 repos	~787	Automated safety check: Pass	MIT	today
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Check PRonyx-dot-app/onyx	32k	2 repos	~2.3k	Automated safety check: Pass	MIT	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	today

Similar skills

PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
32k GitHub starsUsed in 2 repos~2.3k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
69k GitHub starsUsed in 2 repos~1.1k tokens
DevelopmentAuto-check passed
GitHub Review Iteration
prisma/orm
Official
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
48k GitHub stars~2.2k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Project Flow Ops

What does Project Flow Ops do?

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. Project Flow Ops is an agent skill from affaan-m/ECC. 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.

When should I use Project Flow Ops?

Project Flow Ops fits situations like: the user wants backlog control; GitHub-to-Linear coordination.

How do I install Project Flow Ops in Claude Code?

Run `npx skills add affaan-m/ECC --skill project-flow-ops -a claude-code`. Or copy the skill folder (skills/project-flow-ops in affaan-m/ECC) into .claude/skills/project-flow-ops in your project. Claude Code loads it when a task matches its description.

How do I install Project Flow Ops in Codex?

Run `npx skills add affaan-m/ECC --skill project-flow-ops -a codex`. Or copy the skill folder (skills/project-flow-ops in affaan-m/ECC) into .agents/skills/project-flow-ops in your project. Codex loads it when a task matches its description.

Can I use Project Flow Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill project-flow-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-flow-ops, .gemini/skills/project-flow-ops, .github/skills/project-flow-ops and .opencode/skills/project-flow-ops in your project.

What does Project Flow Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: Project Flow Ops is instructions for the agent only.

Does Project Flow Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Project Flow Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Project Flow Ops use?

Project Flow Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Project Flow Ops use?

About 787 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Project Flow Ops?

Skills that share tags, products or a category with Project Flow Ops: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Flow Ops?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Project Flow Ops

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Project Flow Ops

When to Use

Operating Model

Core Workflow

1. Read the public surface first

2. Classify the work

3. Decide whether Linear is warranted

4. Keep the two systems consistent

Review Rules

Output Format

Good Use Cases

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from affaan-m/ECC

Related

Questions about Project Flow Ops