affaan-m/ECC

project-flow-ops

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.

77Collecting

See how to use it View GitHub source

npx skills add https://github.com/affaan-m/ECC --skill "skills/project-flow-ops"

Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn project-flow-ops's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.

npx skills add https://github.com/affaan-m/ECC --skill "skills/project-flow-ops"

Check the pinned source

Best fit

Triage open PR or issue backlogs
Decide what belongs in Linear vs what should remain GitHub-only
Link active GitHub work to internal execution lanes

Bring this context

A concrete task that matches the documented purpose of project-flow-ops.
The files, examples, or context the task depends on.
Your constraints, target environment, and definition of done.

Expected outputs

A result that follows the pinned project-flow-ops instructions.
A concise record of assumptions, inputs used, and unresolved questions.
A final check against the source workflow and relevant permission signals.

Key source sections

Read project-flow-ops through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

Core Workflow

Every item should end up in one of these states:

SKILL.md · Core Workflow

GitHub issue or PR stateauthor and branch statusreview comments

Review Rules

Never merge from title, summary, or trust alone; use the full diff

SKILL.md · Review Rules

Never merge from title, summary, or trust alone; use the full diffExternal-source features should be rebuilt inside ECC when they are valuable but not self-containedCI red means classify and fix or block; do not pretend it is merge-ready

When to Use

Triage open PR or issue backlogs

SKILL.md · When to Use

Triage open PR or issue backlogsDecide what belongs in Linear vs what should remain GitHub-onlyLink active GitHub work to internal execution lanes

Operating Model

GitHub is the public and community truth

SKILL.md · Operating Model

GitHub is the public and community truthLinear is the internal execution truth for active scheduled workNot every GitHub issue needs a Linear issue

1. Read the public surface first

GitHub issue or PR state

SKILL.md · 1. Read the public surface first

GitHub issue or PR stateauthor and branch statusreview comments

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use project-flow-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned project-flow-ops source to [task]. Pay particular attention to these source sections: “Core Workflow”, “Review Rules”, “When to Use”, “Operating Model”, “1. Read the public surface first”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current project-flow-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “Core Workflow” has been checked.

The source section “Review Rules” has been checked.

The source section “When to Use” has been checked.

The source section “Operating Model” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

project-flow-ops

通过分类问题和拉取请求、关联活跃工作、保持GitHub对外可见而Linear作为内部执行层，来协调GitHub和Linear之间的执行流程。当用户需要待办事项控制、PR分类或GitHub与Linear协调时使用。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

project-flow-ops

日本語翻訳：このファイルは project-flow-ops 用の日本語翻訳が必要です

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does project-flow-ops do?

This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.

How do I start using project-flow-ops?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/project-flow-ops". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars

234,327

Repository forks

35,711

Quality

77/100

Source repository last pushed

2026-07-27

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

77/100

Documentation24/30

Specificity16/25

Maintenance20/20

Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

project-flow-ops by affaan-m

日本語翻訳：このファイルは project-flow-ops 用の日本語翻訳が必要です

design-review by event4u-app

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

dask by k-dense-ai

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

medchem by k-dense-ai

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski, Veber, CNS), structural alert catalogs (PAINS, NIBR, ChEMBL), complexity metrics, and the medchem query language for library filtering.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

Project Flow Ops

This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.

Use it when the problem is coordination, not coding.

When to Use

Triage open PR or issue backlogs
Decide what belongs in Linear vs what should remain 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

Operating Model

GitHub is the public and community truth
Linear is the internal execution truth for active scheduled work
Not every GitHub issue needs a Linear issue
Create or update Linear only when the work is:
- active
- delegated
- scheduled
- cross-functional
- important enough to track internally

Core Workflow

1. Read the public surface first

Gather:

GitHub issue or PR state
author and branch status
review comments
CI status
linked issues

2. Classify the work

Every item should end up in one of these states:

State	Meaning
Merge	self-contained, policy-compliant, ready
Port/Rebuild	useful idea, but should be manually re-landed inside ECC
Close	wrong direction, stale, unsafe, or duplicated
Park	potentially useful, but not scheduled now

3. Decide whether Linear is warranted

Create or update Linear only if:

execution is actively planned
multiple repos or workstreams are involved
the work needs internal ownership or sequencing
the issue is part of a larger program lane

Do not mirror everything mechanically.

4. Keep the two systems consistent

When work is active:

GitHub issue/PR should say what is happening publicly
Linear should track owner, priority, and execution lane internally

When work ships or is rejected:

post the public resolution back to GitHub
mark the Linear task accordingly

Review Rules

Never merge from title, summary, or trust alone; use the full diff
External-source features should be rebuilt inside ECC when they are valuable but not self-contained
CI red means classify and fix or block; do not pretend it is merge-ready
If the real blocker is product direction, say so instead of hiding behind tooling

Output Format

Return:

PUBLIC STATUS
- issue / PR state
- CI / review state

CLASSIFICATION
- merge / port-rebuild / close / park
- one-paragraph rationale

LINEAR ACTION
- create / update / no Linear item needed
- project / lane if applicable

NEXT OPERATOR ACTION
- exact next move

Good Use Cases

"Audit the open PR backlog and tell me what to merge vs rebuild"
"Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes"
"Check whether this needs a Linear issue or should stay GitHub-only"

Source repo: affaan-m/ECC
Skill path: skills/project-flow-ops/SKILL.md
Commit SHA: 4e973d3eaf92
Repository license: MIT
Data collected: Jul 28, 2026