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.
The project-flow-ops skill is designed to streamline coordination between GitHub and Linear by creating a unified execution flow from disconnected issues, pull requests, and tasks. It addresses the challenge of managing backlogs and active work across public and internal systems, ensuring that teams maintain clear visibility of progress while keeping internal planning organized. Rather than focusing on coding itself, this skill emphasizes operational control, helping users decide what work should be publicly tracked on GitHub and what requires internal attention in Linear.
Key capabilities of project-flow-ops include triaging open pull requests and issues, linking GitHub work to internal execution lanes, and classifying items into actionable states such as merge, port/rebuild, close, or park. The skill also guides decisions on when to create or update Linear tasks based on activity, delegation, scheduling, cross-functional relevance, or importance. It enforces review rules to prevent premature merging and ensures that CI failures, review comments, or product blockers are correctly reflected in the workflow. Outputs are structured to show public status, classification, Linear action, and next operator actions, providing a clear and actionable summary for users.
This skill is particularly useful for product managers, release coordinators, and engineering leads who need to maintain consistent execution across multiple repositories and teams. Common use cases include auditing PR backlogs, mapping GitHub issues into internal program lanes, and determining which items require a Linear task versus remaining GitHub-only. By providing a structured and consistent approach to workflow management, project-flow-ops helps teams improve visibility, maintain alignment, and reduce the risk of stalled or mismanaged work.
Use this skill when you need to coordinate work across GitHub and Linear, triage backlogs, classify PRs, link active tasks to internal lanes, or audit whether issues are blocking execution.
No. Linear tasks are only created or updated when work is active, delegated, scheduled, cross-functional, or important to track internally. Not every GitHub issue requires a Linear task.
Items can be classified into four states: merge (ready to integrate), port/rebuild (valuable but requires manual handling), close (stale or incorrect), and park (potentially useful but not scheduled).
Yes. Do not merge based on title or summary alone. Assess the full diff, CI status, and review comments. External features that are valuable but not self-contained should be rebuilt internally. CI failures indicate the need to fix or block, not merge prematurely.
The skill is aimed at team leads, product managers, and engineers responsible for backlog management, release coordination, and maintaining execution flow between public GitHub and internal Linear systems.
Quick Setup:
.claude/skills/Repository
affaan-m/everything-claude-code