project-flow-ops

Coordinate GitHub issues and PRs with Linear tasks by triaging open items and linking active work to internal execution lanes. This skill keeps GitHub as the public truth while Linear manages internal execution, applying bi-directional updates to maintain synchronization across both systems.

Triage backlog items by classifying each open GitHub issue or PR into Merge, Port/Rebuild, Close, or Park categories. This classification determines what moves to Linear for internal execution versus what stays on GitHub, maintaining clear execution state across systems.

Keep issues in GitHub only when they do not require internal execution tracking or cross-repo coordination. The triage process classifies items into distinct categories, ensuring only active work that needs internal planning gets linked to Linear lanes.

Cross-system synchronization works through bi-directional updates that link active GitHub work to Linear execution lanes. It audits public feedback and CI outcomes from GitHub while syncing internal planning through Linear, without leaking internal work publicly.

Yes, you can audit and synchronize public feedback, CI outcomes, and internal planning across GitHub and Linear. The skill reconciles these systems while ensuring internal work is not leaked publicly, keeping public and internal execution states aligned.