Coordination
Orchestrate complex work by breaking tasks into lanes and tracking progress across teams.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/coordination-prassanna-ravishankar/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
Use when orchestrating complex or multi-lane work, decomposing tasks across peers, choosing status/board surfaces, running mesh roundups, or keeping high-level progress visible.
What this skill does
Coordination
Coordinate the work shape. Prefer delegation for substantive repo work; small reversible chores may be handled directly when that is the lightest path.
Core loop
- Clarify objective, success criteria, owner, and deadline when missing.
- Split complex work into independent lanes by repo, worktree, risk, or review concern.
- Pick the lightest status surface that will survive the work: existing board, GitHub issue/project, Linear/Jira, Beads, a repo checklist, or a simple markdown board.
- Assign each lane to a peer, worktree, or durable job. Use the worktree-isolation skill when concurrent implementation could overlap files or branches.
- Track only high-level state: owner, status, blocker, next action. Keep transcript details in session history, not the board.
- Round up by impact and blocker, not activity count.
Board guidance
Prefer the user's existing board. Do not invent a new tracker unless the user asks or the work is large enough that status would otherwise be lost.
Useful board columns are simple: Todo, In Progress, Blocked, Review, Done. Entries should describe the outcome, owner, blocker, and next action. Do not mirror every message or tool call.
Mesh roundup
When the user asks where things stand, use list_peers() and ask relevant peers in parallel. Ask specific questions: blocker, next merge, needed decision. Compile the reply with the highest-impact item first. Keep Telegram/mobile updates short.
Anti-patterns
- Serializing independent lanes behind the orchestrator.
- Letting the orchestrator drift into implementation when a peer should own the lane.
- Writing board or memory updates just because a turn ended.
- Count-leading summaries that reward volume over impact.
Related skills
App Store Listing Audit
coreyhaines31
Analyze your app listing against best practices and get a prioritized optimization plan.
Co-Marketing Partnerships
coreyhaines31
Find ideal partners and plan joint marketing campaigns with other companies.
Cold Email Writer
coreyhaines31
Write B2B cold emails and follow-up sequences designed to get replies.
Community-Led Growth
coreyhaines31
Build and grow online communities to drive product adoption and customer loyalty.