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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Project Flow Ops when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Project Flow Ops when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/project-flow-ops # Save SKILL.md to ~/.claude/skills/project-flow-ops/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/project-flow-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/project-flow-ops/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Project Flow Ops skill for this task: Triage open PR or issue backlogs. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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.
### 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"
Intended uses
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.