Staff Meeting skill

Coordinate cross-repo staff meetings with phase-driven negotiation and artifact storage.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/vm-wylbur/claude-negotiate --skill staff-meeting-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Staff Meeting skill
Source: https://github.com/vm-wylbur/claude-negotiate/tree/main/skills/staffmtg
Command: npx skills add https://github.com/vm-wylbur/claude-negotiate --skill staff-meeting-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staff teams coordinating across multiple repositories often face scattered alignment, unclear priorities, and duplicated work. This skill provides a repeatable workflow to open, run, and converge a cross-repo staff meeting with a formal negotiation process.

Core Features & Use Cases

  • Phase-driven negotiation workflow that collects participant surveys, builds dependency graphs, and surfaces blockers.
  • Cross-repo coordination with explicit artifact recording in claude-mem for traceability.
  • Objection handling and sub-negotiations to resolve conflicting config decisions.

Quick Start

Say "ok staffmtg" to begin the staff meeting workflow and load the cross-repo planning process.

Frequently Asked Questions about Staff Meeting skill

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

FAQPage Schema
How do I coordinate cross-repo staff meetings to negotiate project dependencies?▼

A phase-driven negotiation workflow coordinates cross-repo staff meetings by collecting participant surveys, building dependency graphs, and resolving conflicts. Meeting artifacts are recorded in claude-mem for traceability.

What is the best way to map dependencies across multiple repositories for priority alignment?▼

The best way to map dependencies across repositories is a formal negotiation workflow that surveys participants and builds a dependency graph. This process surfaces blockers and aligns priorities for cross-repo projects.

How does the consensus-building workflow handle objection resolution during cross-repo negotiations?▼

Objection resolution during cross-repo negotiations is handled through explicit objection handling and sub-negotiations to resolve conflicting configuration decisions. The workflow uses convergent closure to finalize agreements.

Can I use this staff meeting workflow without setting up any external dependencies?▼

Yes, you can use this staff meeting workflow without external dependencies, as it requires none to run. Trigger the workflow to load the cross-repo planning process and begin the negotiation phases.

What phases are involved in running a cross-repo staff meeting for conflict resolution?▼

The phases involved in running a cross-repo staff meeting are historian, open meeting, surveys, synthesis, and convergent closure. These structured phases facilitate conflict resolution and consensus-building.

How to ensure traceability of priority decisions made during cross-repo project negotiations?▼

To ensure traceability of priority decisions, store meeting artifacts in claude-mem. This explicit artifact recording captures the negotiation process and convergent closure outcomes for cross-repo projects.