team-coordination

Define Scrum team roles, escalation paths, and decision governance.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/tuanldas/superteam --skill team-coordination-tuanldas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-coordination
Source: https://github.com/tuanldas/superteam/tree/main/skills/team-coordination
Command: npx skills add https://github.com/tuanldas/superteam --skill team-coordination-tuanldas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Team coordination and governance for Scrum-based projects, clarifying roles, escalation paths, and cross-team communication to prevent chaos and misalignment.

Core Features & Use Cases

  • Defines role boundaries and decision hierarchy for Scrum teams.
  • Provides a standardized Task lifecycle, context loading order, and deviation handling rules.
  • Supports integration with /st:team for team creation, routing, and pipeline coordination across projects.

Quick Start

Run /st:team create to assemble your team profile.

Frequently Asked Questions about team-coordination

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

FAQPage Schema
How do I establish a clear decision hierarchy and escalation paths for Scrum teams?

To establish a clear decision hierarchy and escalation paths for Scrum teams, define role boundaries, decision governance, and standardized deviation handling to prevent misalignment and cross-role communication chaos.

What is the standardized context loading order for task lifecycles in team coordination?

The standardized context loading order enforces a specific sequence for task lifecycles, ensuring cross-role communication, context sharing, and deviation handling keep team configurations aligned during Scrum execution.

How do I coordinate cross-team communication and routing across multiple Scrum projects?

Coordinate cross-team communication and routing by integrating team creation, pipeline coordination, and optional role adaptation rules to manage task lifecycles and maintain alignment across multiple projects.

Does this team coordination approach support optional roles and adaptation rules for different team configurations?

Yes, this team coordination approach supports optional roles and adaptation rules, allowing customized task lifecycles, context sharing, and cross-role communication across various Scrum team configurations.

What is the best way to prevent chaos and misalignment in Scrum-based project governance?

The best way to prevent chaos and misalignment in Scrum-based project governance is to enforce standardized context loading, define clear role boundaries, and establish decision governance with explicit escalation paths.