cross-functional-collaboration
Skill0 starsChanged 7 months agoMITView on GitHub
Coordinate R&D, design, marketing, and operations teams to establish efficient collaboration mechanisms and eliminate communication barriers.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Contextual Consistency: Ensure everyone understands "why we are doing this."
- Distinctive: line 20
Transparency: All decision-making processes and progress must be visible to the entire team.
- Distinctive: line 21
Resolve Conflicts, Don't Evade: Use metrics and experimental data to arbitrate cross-functional disagreements.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cross-functional Collaboration: Collaboration and Consensus Building
Break down silos and establish a shared sense of purpose.
Checklist
- Define RACI Matrix — Clarify who is Responsible (R), Accountable (A), Consulted (C), and Informed (I).
- Establish Feedback Loops — Set up fixed cross-departmental synchronization mechanisms.
- Eliminate Jargon Barriers — Translate technical terms into business value and vice versa.
- Risk Warning Mechanism — When one department encounters a blocker, how is a timely response from others ensured?
Core Mandates
- Contextual Consistency: Ensure everyone understands "why we are doing this."
- Transparency: All decision-making processes and progress must be visible to the entire team.
- Resolve Conflicts, Don't Evade: Use metrics and experimental data to arbitrate cross-functional disagreements.
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.