project-flow-ops

Coordinates GitHub issues/PRs and Linear tasks into a unified execution flow for triage and classification.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill project-flow-ops-richardnpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/richardnpaul/everything-vscode-copilot/tree/main/.github/skills/project-flow-ops
Command: npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill project-flow-ops-richardnpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate disjoint GitHub issues, PRs, and Linear tasks into one execution flow to improve backlog control and cross-tool coordination.

Core Features & Use Cases

  • Triages open PR backlogs and issues
  • Decide what belongs in Linear vs 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

Quick Start

Triages a set of open GitHub issues and PRs to map active work to Linear lanes.

Frequently Asked Questions about project-flow-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate GitHub issues and Linear tasks into a single backlog flow?

To coordinate GitHub and Linear backlog flow, triage open PRs and issues to map active work into internal execution lanes, syncing public GitHub visibility with internal Linear planning.

How do I triage GitHub PRs to decide between merging, porting, closing, or parking?

Triage GitHub PRs by reading repository state, author status, CI results, and linked issues to classify work into Merge, Port/Rebuild, Close, or Park actions, updating Linear accordingly.

When should I keep a task in Linear versus leaving it as a GitHub-only issue?

Decide whether Linear is warranted by auditing review comments, CI failures, and stale issues. If work requires internal execution lanes and governance, it belongs in Linear; otherwise, it stays GitHub-only.

Does this GitHub and Linear triage workflow require any specific dependencies or components?

No dependencies or components are required. The workflow operates by reading GitHub state, author status, and CI results to determine actions and update Linear tasks without external integrations.

What is the best way to audit blocking review comments and CI failures across GitHub and Linear?

Audit blocking review comments and CI failures by reading GitHub state and linked issues to determine execution blockers, then update Linear planning to reflect the corrected backlog flow.