agentsclimarketplace

Align cross team communication

Skill alexe-ev/product-plugins/product-ops/skills/align-cross-team-communication

Skill library for AI agents — 15 product domains, 121 skills. Tells the agent what to ask, how to reason, and what to output.

Install
npx -y skills add alexe-ev/product-plugins --skill align-cross-team-communication

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design communication systems and rituals that keep product, engineering, design, and business teams aligned. Use this skill when cross-team communication is breaking down or misalignment is creating delivery problems.

SKILL.md

2.4 KB, as published. Nobody here has run it

Align Cross-Team Communication

Purpose

Help teams design effective communication systems that maintain alignment across product, engineering, design, and business stakeholders without creating overhead.

Skill type

Conceptual skill

Use this skill when

  • Teams are working in silos and discovering misalignment late
  • Engineering builds the wrong thing because product communication is unclear
  • Stakeholders are surprised by product decisions or status
  • A new cross-functional team needs communication norms established

Do not use this skill when

  • The goal is executive communication and narrative (use build-executive-narrative)
  • The goal is operating cadence design (use design-operating-cadence)

Required inputs

  • Teams involved in cross-functional work
  • Current communication pain points or failure modes

Optional inputs

  • Current communication channels and tools
  • Stakeholder types and needs
  • Meeting cadence

Upstream context

Works best when:

  • Operating cadence is designed
  • Team structure is clear

Downstream handoff

Output can feed:

  • design-team-rituals
  • manage-tooling-documentation

Instructions

  1. Map all cross-team communication flows: who needs what information, how often, in what format.
  2. Identify current breakdown points (where misalignment happens most).
  3. Design synchronous and async communication channels for each flow.
  4. Define norms for decision communication: who is informed, consulted, and accountable.
  5. Design status update and escalation protocols.
  6. Define feedback loops back to product from engineering and design.

Output

Provide:

  • Communication flow map (who needs what, when, how)
  • Current breakdown points
  • Recommended communication channels by type
  • Decision communication norms (RACI or similar)
  • Status update and escalation protocol
  • Feedback loop design from engineering/design to product

Risks / caveats

  • More communication channels is not better alignment — reduce noise, increase signal
  • Decisions that aren't communicated still need to be justified — design for transparency
  • Async-first works well but requires strong written communication norms

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.