project-flow-ops

Coordinate GitHub issues and pull requests with Linear execution lanes.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill project-flow-ops-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/project-flow-ops
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill project-flow-ops-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination problem of scattered work across GitHub issues/PRs and Linear tasks, so teams can reliably triage, classify, and assign active execution instead of losing context or duplicating effort.

Core Features & Use Cases

  • GitHub-to-Linear execution alignment: Treat GitHub as the public surface and Linear as the internal execution lane for scheduled, delegated, and cross-functional work.
  • PR/issue classification for next actions: Decide whether work should be merged, port/rebuilt in the ECC system, closed, or parked based on diff quality, CI, and staleness signals.
  • Operational auditing for blockers: Evaluate whether review comments, CI failures, or outdated items are blocking execution and ensure outcomes are reflected back publicly.

Quick Start

Ask the skill to audit your open GitHub PRs and issues, classify each one into merge/port-rebuild/close/park, and specify whether a matching Linear item should be created or updated.

Frequently Asked Questions about project-flow-ops

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

FAQPage Schema
How do I align GitHub pull requests with Linear execution lanes?▼

To align GitHub pull requests with Linear execution lanes, you triage and classify each PR by diff quality, CI status, and staleness, then link it to a matching Linear task. This ensures consistent public-to-internal state updates and prevents duplicated effort.

What is the best way to triage a GitHub issue backlog for internal execution?▼

Triageing a GitHub issue backlog for internal execution involves evaluating each issue's staleness and review comments to classify it as merge, port-rebuild, close, or park. This determines what moves into Linear execution versus stays GitHub-only.

How do I classify GitHub PRs to decide between merging, porting, or closing?▼

Classifying GitHub PRs to decide between merging, porting, or closing relies on evaluating diff quality, CI failures, and staleness signals. This classification outputs a structured status, rationale, and next operator action for each pull request.

Does coordinating GitHub and Linear require a full-diff review posture?▼

Yes, coordinating GitHub and Linear requires a full-diff review posture to accurately evaluate blockers like review comments and CI failures. This strict review ensures operational auditing reflects outcomes back publicly without losing context.

Can I use this workflow orchestration for RBAC coordination across GitHub and Linear?▼

Yes, you can use this workflow orchestration for RBAC coordination across GitHub and Linear by treating GitHub as the public surface and Linear as the internal execution lane. It enforces consistent state updates for cross-functional delegated work.