project-flow-ops

Coordinate GitHub issues and PRs with Linear tasks for execution flow.

2|Updated Mar 3, 2026

Search Tags:#workflow #github #backlog #linear #triage #cross-system #pr-management

Ready to run

npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill project-flow-ops-momodaviluke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/project-flow-ops
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill project-flow-ops-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Triage open PRs and issues to determine what belongs in Linear vs. what should stay on GitHub
Link active GitHub work to internal Linear tasks to preserve execution context
Audit and synchronize public GitHub state with internal Linear planning to improve cross-team coordination

Quick Start

Triage open PRs and link relevant GitHub issues to Linear tasks to establish the execution flow.

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 pull requests with Linear tasks?▼

To coordinate GitHub and Linear, triage open PRs and issues to decide what stays public versus moves into Linear for internal tracking. Link active GitHub work to Linear tasks to preserve execution context and synchronize public state with internal planning.

When should I keep an issue on GitHub instead of moving it to Linear?▼

Keep an issue on GitHub when it belongs on the public-facing surface, and move it to Linear when it requires internal execution tracking. Triage open PRs and issues to classify whether work needs internal planning or should remain visible to the public.

How do I triage pull requests across multiple repositories for backlog control?▼

Triage pull requests by classifying each one into governance categories like merge, port/rebuild, close, or park. This guides whether to create or update Linear items and reflects the public GitHub status in Linear for cross-team coordination.

Can I use Linear as an internal execution layer while keeping GitHub public-facing?▼

Yes, you can use Linear as the internal execution layer while keeping GitHub public-facing. Audit and synchronize public GitHub state with internal Linear planning to align the public surface with internal execution lanes for better coordination.

What is the best way to link active GitHub work to internal Linear planning?▼

The best way to link active GitHub work to Linear is by triaging open PRs and linking relevant GitHub issues to Linear tasks. This establishes the execution flow and preserves context across multiple repos by reflecting GitHub status in Linear.

How does PR classification work when synchronizing GitHub state with Linear?▼

PR classification enforces governance by categorizing pull requests as merge, port/rebuild, close, or park. It guides when to create or update Linear items and determines how to reflect the public GitHub status within Linear's internal execution lanes.