nw-collaboration-and-handoffs

Coordinate cross-agent handoffs with defined patterns and commit message formats.

Updated Apr 15, 2026

Search Tags:#collaboration #TDD #refactoring #workflows #handoffs #cross-agent #Mikado

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-collaboration-and-handoffs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-collaboration-and-handoffs
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-collaboration-and-handoffs
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-collaboration-and-handoffs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and streamlines cross-agent collaboration and handoffs between roles like acceptance designer, solution architect, and feature completion coordinator, reducing miscommunication and handoff delays.

Core Features & Use Cases

Defines cross-agent handoff patterns (TDD to Mikado, TDD to Refactoring, Mikado to Systematic Execution) and the Integrated Workflow Patterns
Specifies clear handoff content, transition steps, and required inputs/outputs to preserve business value during refactors and feature delivery
Establishes consistent commit message formats to improve traceability and collaboration across teams

Quick Start

Align your development workflow with the four handoff patterns and adopt the standardized commit messages to improve handoff quality.

Frequently Asked Questions about nw-collaboration-and-handoffs

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

FAQPage Schema

How do I manage cross-agent handoffs between design and implementation workflows?▼

Cross-agent handoffs are managed by defining standardized transition patterns between roles like solution architect and feature coordinator, ensuring clear input/output definitions. This reduces miscommunication and preserves business value during feature delivery.

What are the standard handoff patterns for TDD to Mikado workflows?▼

Standard handoff patterns for TDD to Mikado workflows specify required transition steps and handoff content to synchronize test-driven development with systematic dependency resolution. These patterns ensure continuous traceability across complex refactoring cycles.

How do you preserve business value during cross-agent refactoring cycles?▼

Preserve business value during refactoring cycles by establishing clear handoff content and required inputs/outputs between cross-agent roles. Consistent commit message formats further improve traceability and collaboration across teams during the refactor.

Do I need defined commit message formats for architecture reviews and handoffs?▼

Defined commit message formats are required for architecture reviews and handoffs to improve collaboration traceability across teams. Standardized messages ensure clear transition steps and role-specific input/output definitions during systematic execution.