Agent skill

Team Routes

by VKirill in VKirill/claude-lane-stack

dev-orchestrator only. An agent skill from VKirill/claude-lane-stack.

MITAuto-check passedAgent Workflows

Install Team Routes

skills CLI
$ npx skills add VKirill/claude-lane-stack --skill team-routes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install VKirill/claude-lane-stack team-routes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .claude/skills/team-routes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
team-routes
GitHub stars
122
Token cost
~1.1k tokens
SKILL.md length
587 words
Files
3 (incl. references)
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

dev-orchestrator only. An agent skill from VKirill/claude-lane-stack.

  • Works in 6 steps: Name the deliverable → Pick or compose a route → Announce and start → …
  • Agent Workflows work in your project
  • SKILL.md covers 1. Name the deliverable, 2. Pick or compose a route, 3. Announce and start and 4. Brief each specialist, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Routes is an agent skill from VKirill/claude-lane-stack. dev-orchestrator only. Turns any request into a route of specialist and writer steps: which roles work, in what order, what each reads and writes. Use at the start of every new goal. SKIP: writer CLIs; specialists themselves.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/recipes.md` and `references/roles.md`).

It sits in Agent Workflows. The repository describes itself as: Multi-agent AI coding factory for one person — Claude Code PM + Codex/Qwen/Grok/Kimi/AGY writers, durable conveyor, auto-merge to main. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/team-routes”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Name the deliverable
  2. Pick or compose a route
  3. Announce and start
  4. Brief each specialist
  5. Merge the outputs
  6. Hand over

What it can do on your machine

Read from SKILL.md and the folder at commit 45fa19e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Routes loads about 1.1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 587 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from VKirill/claude-lane-stack at commit 45fa19e, republished under its MIT licence (© VKirill). 587 words, ~1,132 tokens.

Download SKILL.mdSave it as .claude/skills/team-routes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
team-routes
description
dev-orchestrator only. Turns any request into a route of specialist and writer steps: which roles work, in what order, what each reads and writes. Use at the start of every new goal. SKIP: writer CLIs; specialists themselves.

Team routes

The operator states a goal, not a staffing plan. You decide who works on it. A page built without its SEO, UX and copy inputs comes back as placeholders and gets redone; a one-line fix sent through four specialists burns an hour of expensive models. Pick the smallest team that produces the artifact the operator actually needs.

1. Name the deliverable

Before Score/Decompose, write one line for yourself: deliverable: <artifact> · surface: <page/app/feature> · slug: <kebab-slug>.

The deliverable is what the operator will open at the end: a gray prototype, a branded mockup, shipped code, an article, an audit report, an answer with sources. Ambiguous wording («сделай страницу») means the cheapest deliverable that still moves the goal (prototype before code) unless the operator said «в код», «на сайт», «задеплой» or the page already exists in code.

2. Pick or compose a route

Start from the closest recipe in references/recipes.md. Drop a step when its output already exists on disk and is not stale (for example .agents/copy/pages/<slug>.md is there, so copy only fills gaps). Add a step when the goal needs a role the recipe lacks. No recipe fits → compose a route from the role cards in references/roles.md: each step's inputs must be outputs of earlier steps or existing files.

Run steps in parallel when neither reads the other's output. Run them in order when one decides what the next one writes about (SEO intent before copy).

Not every request needs a route. Go straight to the existing Loop when the goal is product code with no new user-facing text or layout (bug, refactor, API, infra), or a question you can answer from the repo.

3. Announce and start

Post one Russian line, then start the first step in the same turn. Do not wait for approval: the operator asked for the result, and the line exists so they can redirect you.

text
Маршрут: seo ∥ design-lead (UX) → copy-lead → design-lead (прототип) → design-lead (аудит). Начинаю.

For routes with 2+ specialist steps, also write the route file .agents/plans/routes/<slug>.md (English):

text
goal: <operator goal, one line>
deliverable: <artifact>
steps:
  - id: seo | role: seo-specialist | reads: [...] | writes: <path> | status: todo
  - ...
decisions: []   # conflicts you resolved, with the reason

Update status after each step. It is how resume-project and a restarted session know where the route stopped.

Show full SKILL.md (245 more words)Show less

4. Brief each specialist

Every specialist prompt has the same five lines. The specialist sees only this prompt and the disk, so a missing READ path means the work is done blind.

text
GOAL: <operator goal + this step's part of it>
SLUG: <slug>
READ: <outputs of earlier steps and existing project files, as paths>
WRITE: <the one path this step owns>
DECIDE: <the questions this step must answer for the next step>

Close with the role's normal sentinel (DONE <path> / FAILED <reason>). Read the file from DONE, not the chat summary, before you start the next step.

5. Merge the outputs

Specialists do not talk to each other. You merge their outputs. When two outputs conflict (SEO wants a long FAQ block, design wants one short screen), decide by the deliverable's primary user action, record the call in decisions: with one reason, and pass it to the next step through READ/DECIDE.

Ask the operator only for what no role can produce from the disk or the web: prices, guarantees, the offer, legal claims, brand approval, money or irreversible actions. Specialists must mark unknown facts [unknown], not invent them. Collect those markers into one question for the operator at the end of the route, not after each step.

6. Hand over

End the route with the deliverable path, what each role contributed (one line each), open [unknown] facts, and the next sensible step (for example «в код — скажи "делай"»). A route that ends in code continues into the normal WRITE Loop: specialist steps finish first, then run-init (Lane Pilot: lane_pilot_dispatch_writer, specialists via lane_pilot_specialist) with their outputs in read_first. This keeps the Mode XOR rule: no research teammates on a goal once its write run has started.

© VKirill, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/lane-stack/skills/team-routes of VKirill/claude-lane-stack.

  • SKILL.md
  • references/recipes.md
  • references/roles.md

Open the folder on GitHubat commit 45fa19e

Compare with similar skills

Team Routes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Routes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Routes this skillVKirill/claude-lane-stack122—~1.1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k36 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 36 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from VKirill/claude-lane-stack

All 49 skills in this repo
  • UI UX Pro Max

    VKirill/claude-lane-stack

    Lane-stack design + brand intelligence (vendored ui-ux-pro-max).

    122 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • App Architect

    VKirill/claude-lane-stack

    Owner-facing architect for a new app or service. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Browser QA

    VKirill/claude-lane-stack

    Live browser QA + Playwright-compatible replay. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Copy Project Life

    VKirill/claude-lane-stack

    Карта файлов копирайта в .agents/copy/: шаблоны, статусы, цепочка audience→headlines→ux.

    122 GitHub stars~534 tokensUpdated yesterday
    Auto-check passed
  • Copy Research

    VKirill/claude-lane-stack

    Dispatch copy-lead helpers: Tavily, Codex luna/terra, grok/X, OpenCode DeepSeek, Cursor Grok 4.6 medium-fast.

    122 GitHub stars~827 tokensUpdated yesterday
    Auto-check passed
  • Docs Maintain

    VKirill/claude-lane-stack

    Keep living docs/ honest after code changes. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~459 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Team Routes

What does Team Routes do?

dev-orchestrator only. An agent skill from VKirill/claude-lane-stack. Team Routes is an agent skill from VKirill/claude-lane-stack. dev-orchestrator only.

When should I use Team Routes?

Team Routes fits situations like: agent Workflows work in your project.

How do I install Team Routes in Claude Code?

Run `npx skills add VKirill/claude-lane-stack --skill team-routes -a claude-code`. Or copy the skill folder (plugins/lane-stack/skills/team-routes in VKirill/claude-lane-stack) into .claude/skills/team-routes in your project. Claude Code loads it when a task matches its description.

How do I install Team Routes in Codex?

Run `npx skills add VKirill/claude-lane-stack --skill team-routes -a codex`. Or copy the skill folder (plugins/lane-stack/skills/team-routes in VKirill/claude-lane-stack) into .agents/skills/team-routes in your project. Codex loads it when a task matches its description.

Can I use Team Routes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VKirill/claude-lane-stack --skill team-routes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-routes, .gemini/skills/team-routes, .github/skills/team-routes and .opencode/skills/team-routes in your project.

What does Team Routes need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Routes is instructions for the agent only.

Does Team Routes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Routes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Team Routes use?

Team Routes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Routes use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Team Routes?

Skills that share tags, products or a category with Team Routes: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Routes?

VKirill (a GitHub user) maintains it in VKirill/claude-lane-stack, which has 122 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: VKirill/claude-lane-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.