flow-router

Determine L1/L2/L3 lanes for code-change requests and delegate accordingly.

5|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/ql-link/LinkRag --skill flow-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-router
Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/flow-router
Command: npx skills add https://github.com/ql-link/LinkRag --skill flow-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the entry gate for the development pipeline, performing a lightweight triage of any code-change request to determine the appropriate lane (L1/L2/L3) based on the change type. It outputs a lane conclusion and the recommended next skill, and it does not generate documentation.

Core Features & Use Cases

  • Lightweight pre-flight triage that assesses the change type and scope to decide whether to use a fast-track or full-chain process.
  • Outputs a clear lane verdict plus the next skill to hand off to, enabling seamless handoffs in the delivery workflow.
  • Serves as the入口 for the entire "需求 → 交付" chain by routing requests to the correct downstream skill without producing interim documents.

Quick Start

Provide a code-change request to trigger triage and receive a lane verdict plus the next step.

Frequently Asked Questions about flow-router

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

FAQPage Schema
How do I automate triage for code-change requests to determine the development lane?

Automate code-change request triage by providing the request to the flow-router, which assesses the change type and scope to output a lane verdict and the recommended next skill.

When do I need flow routing to select between a fast track and a full chain process?

You need flow routing when a code-change request requires lane selection to decide if it qualifies for a fast track (L1) or needs a full chain (L2/L3) based on its scope.

What is the best way to handle lane selection for incoming code changes without generating documentation?

The best way to handle lane selection without documentation is to apply lane rules to the code-change request, returning only a lane conclusion and the recommended next station.

Can I use automated triage to route code changes directly to downstream delivery skills?

Yes, you can use automated triage to route code changes by returning a lane conclusion and delegating the request to the corresponding downstream skill for seamless handoffs.

Does the lane selection process output any interim documents or reports?

No, the lane selection process does not generate any documentation or interim reports; it strictly outputs a lane conclusion and the recommended next skill for the delivery workflow.

What are the limitations of using lightweight pre-flight triage for code-change requests?

The limitation of lightweight pre-flight triage is that it only provides a lane verdict and next step recommendation without generating documentation or executing the actual code change.