Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

team-coordination

Étoiles1

Forks0

Mis à jour24 mai 2026 à 16:31

Use when managing an ACTIVE agent team — coordinating tasks between teammates, handling team messaging, plan approval, delegate mode, display modes, or graceful shutdown. Triggers: "task management", "team communication", "delegate mode", "plan approval", "shutdown teammates", "team messaging", "how do I manage my team", "feedback gate", "dedup guard". Do NOT trigger for choosing a team blueprint or describing what agent teams are at a high level — those route to `team-blueprints` and `agent-teams` respectively. This skill is for running a team that's already spawned.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

nthplusio

nthplusio/functional-claude

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

Explorateur de fichiers

5 fichiers

SKILL.md

readonly

name	team-coordination
description	Use when managing an ACTIVE agent team — coordinating tasks between teammates, handling team messaging, plan approval, delegate mode, display modes, or graceful shutdown. Triggers: "task management", "team communication", "delegate mode", "plan approval", "shutdown teammates", "team messaging", "how do I manage my team", "feedback gate", "dedup guard". Do NOT trigger for choosing a team blueprint or describing what agent teams are at a high level — those route to `team-blueprints` and `agent-teams` respectively. This skill is for running a team that's already spawned.
version	0.26.0

Team Coordination Patterns

Operating manual for active agent teams. Covers task lifecycle, communication, plan approval, hook-based quality gates, and graceful shutdown.

Quick router

You want to...	Read
Manage the task list (states, assignment, sizing, dependencies, dedup guard)	references/task-management.md
Message teammates, choose between message vs broadcast, switch display modes	references/communication.md
Understand team startup → operation → shutdown flow, including delegate mode	references/lifecycle.md
Enforce plan approval, user feedback gates, or use TaskCreated/Idle/Completed hooks	references/quality-gates.md

Where canonical protocols live

This skill describes how coordination works. The literal protocol blocks teammates receive at spawn time are in:

${CLAUDE_PLUGIN_ROOT}/shared/core-protocols.md — the four canonical Protocol Blocks (Task Blocking, Escalation, Output Standards, Shutdown). Every spawn prompt embeds this via [Include Core Protocols from shared/core-protocols.md].
${CLAUDE_PLUGIN_ROOT}/shared/shutdown-protocol.md — full shutdown sequence including Phase 0 scenario invalidation check.
${CLAUDE_PLUGIN_ROOT}/shared/efficiency-guidelines.md — right-sizing rules, coordination overhead budget, anti-patterns.
${CLAUDE_PLUGIN_ROOT}/shared/artifact-protocol.md — docs/teams/[team]/ directory structure and frontmatter schemas.

Edit those files when changing rules. This skill's references describe behavior in plain language for human readers.

Plus depuis ce dépôt

même dépôt

pm-branches

nthplusio/functional-claude

Use this skill when creating a git branch for a Linear or GitHub issue, writing a PR description, opening a pull request, or linking a PR to its tracked issue. Trigger phrases "create a branch", "new branch for this issue", "branch for

2026-06-091

pm-conventions

nthplusio/functional-claude

Use this skill when integrating, reading, or updating a project's conventions.md file — the document that captures house style for issue titles, labels, branch naming, PR descriptions, handoff phrasing, and review etiquette. Trigger phrases "set conventions", "load conventions", "where are the conventions", "what are our conventions", "add a convention", "edit conventions.md", "/pm-conventions", "the conventions say", "our team uses <X> format", "project conventions", "project title format". Also use proactively when another pm-* skill (pm-issues, pm-review, pm-improve, pm-branches, pm-handoff, pm-agent, pm-projects, pm-project-review) is about to write or evaluate text and a conventions file exists at `<repo>/.claude/pm/conventions.md` — the conventions must be loaded and applied before the skill writes anything user-facing.

2026-06-091

pm-dedup

nthplusio/functional-claude

Use this skill when the user asks to "find duplicate issues", "clean up duplicates", "what dupes are in the backlog", "/pm-dedup", or after a /pm-status briefing flags likely-dup clusters. Runs the `duplicates` lens against the team cache, has the agent judge each cluster, then offers merge / relate / close per cluster. Powered by the shared dedup engine in `hooks/lib/dedup.js`.

2026-06-091

pm-feedback

nthplusio/functional-claude

Use this skill when the user wants to report a bug, an unexpected result, or an improvement idea about the project-manager plugin ITSELF (or one of its pm-* skills) to the functional-claude maintainers — or when the agent has just hit a project-manager failure (a pm-* CLI error, a wrong/empty briefing, a crash, a clearly-incorrect result) and should offer to report it. Trigger phrases "report a bug in pm-review / pm-notes / any pm-* skill", "this plugin is broken", "pm gave the wrong answer", "send feedback about project-manager", "tell the functional-claude team", "/pm-feedback", "file a plugin issue". The defining cue is that the target of the complaint is the plugin or a named pm-* skill, not the user's own product. Assembles a README-shaped report (plugin + version, repro, expected vs actual, safe environment), scrubs every credential via the tested `hooks/lib/feedback-report.js` guard, previews it, then delivers — email to the Linear intake address (via resend-cli), GitHub issue fallback, or copy-paste d

2026-06-091

pm-handoff

nthplusio/functional-claude

Use this skill when the user wants to hand off work to another person or to the next stage of the lifecycle. Trigger phrases "hand this off to", "give this to", "I'm OOO", "passing this to", "covering for", "ready for release", "ready for QA", "ready for review", "release notes", "deploy handoff", "write a handoff", "/pm-handoff". Produces recipient-facing briefs with four required blocks (summary, what's done + how to use it, what's NOT done + next steps, open questions). Routes through configured channels (Linear, GitHub, markdown, chat/email).

2026-06-091

pm-improve

nthplusio/functional-claude

Distinct from `pm-review` (which *scores* whether an issue has the right structural shape), this skill *adds* project-specific context to an existing Linear or GitHub issue — relevant files, recent commits, owning modules, best-practice references, prior-art / related issues, and clarifying questions the author should answer before work starts. Use it when you want to give an issue more material to work from, not when you want to grade it. Trigger phrases "improve this issue", "enrich issue <ID>", "add context to this issue", "what's missing from this issue", "any relevant code for this issue", "research this issue", "qna this issue", "/pm-improve". Also use proactively after `pm-review` flags structural gaps that hint at missing context. Produces a draft enrichment; with `--apply`, posts it as a comment on the issue. Safe to re-run as repo state drifts — the marker mechanic replaces rather than stacks.

2026-06-091

name	team-coordination
description	Use when managing an ACTIVE agent team — coordinating tasks between teammates, handling team messaging, plan approval, delegate mode, display modes, or graceful shutdown. Triggers: "task management", "team communication", "delegate mode", "plan approval", "shutdown teammates", "team messaging", "how do I manage my team", "feedback gate", "dedup guard". Do NOT trigger for choosing a team blueprint or describing what agent teams are at a high level — those route to `team-blueprints` and `agent-teams` respectively. This skill is for running a team that's already spawned.
version	0.26.0

Team Coordination Patterns

Operating manual for active agent teams. Covers task lifecycle, communication, plan approval, hook-based quality gates, and graceful shutdown.

Quick router

You want to...	Read
Manage the task list (states, assignment, sizing, dependencies, dedup guard)	references/task-management.md
Message teammates, choose between message vs broadcast, switch display modes	references/communication.md
Understand team startup → operation → shutdown flow, including delegate mode	references/lifecycle.md
Enforce plan approval, user feedback gates, or use TaskCreated/Idle/Completed hooks	references/quality-gates.md

Where canonical protocols live

This skill describes how coordination works. The literal protocol blocks teammates receive at spawn time are in:

${CLAUDE_PLUGIN_ROOT}/shared/core-protocols.md — the four canonical Protocol Blocks (Task Blocking, Escalation, Output Standards, Shutdown). Every spawn prompt embeds this via [Include Core Protocols from shared/core-protocols.md].
${CLAUDE_PLUGIN_ROOT}/shared/shutdown-protocol.md — full shutdown sequence including Phase 0 scenario invalidation check.
${CLAUDE_PLUGIN_ROOT}/shared/efficiency-guidelines.md — right-sizing rules, coordination overhead budget, anti-patterns.
${CLAUDE_PLUGIN_ROOT}/shared/artifact-protocol.md — docs/teams/[team]/ directory structure and frontmatter schemas.

Edit those files when changing rules. This skill's references describe behavior in plain language for human readers.