persona-coordination

Coordinate multi-persona collaboration for OpenSpec planning and beads-based execution.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill persona-coordination
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-coordination
Source: https://github.com/cmtkdot/arc/tree/main/skills/persona-coordination
Command: npx skills add https://github.com/cmtkdot/arc --skill persona-coordination

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Arc's eight expert personas for cohesive OpenSpec planning, beads decomposition, and team execution, ensuring timely handoffs and conflict resolution.

Core Features & Use Cases

  • Orchestrates persona roles (backend-architect, frontend-developer, security-auditor, persona-typescript-pro, persona-tdd-orchestrator, persona-debugger, persona-research-synthesizer, persona-ux-researcher) for OpenSpec planning and bead design
  • Defines clear handoffs, dependencies, and coordination rules to keep multi-persona workflows aligned
  • Supports conflict resolution workflows and escalation when design decisions become untestable or blocked
  • Produces unified OpenSpec artifacts and bead plans that reflect cross-persona alignment

Quick Start

Start a cross-persona OpenSpec planning session and generate coordinated bead plans for the next milestone.

Frequently Asked Questions about persona-coordination

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

FAQPage Schema
How do I coordinate cross-functional team workflows for OpenSpec planning?

Cross-functional team workflows for OpenSpec planning are coordinated by orchestrating expert personas, defining handoffs, and aligning bead dependencies for cohesive execution.

What is the best way to manage persona handoffs during beads-based execution?

Persona handoffs during beads-based execution are managed by defining explicit dependencies and coordination rules across backend, frontend, security, and research roles.

Can I use this to resolve conflicts when design decisions become untestable or blocked?

Yes, conflict resolution and escalation workflows are triggered when design decisions become untestable or blocked, ensuring cross-persona alignment remains on track.

How do I sequence cross-cutting tasks for backend, frontend, and TDD personas?

Cross-cutting tasks for backend, frontend, and TDD personas are sequenced by mapping explicit bead dependencies and applying cross-functional coordination rules.

Does this workflow require predefined OpenSpec artifacts before starting?

No, this workflow produces unified OpenSpec artifacts and bead plans that reflect cross-persona alignment, generating the required provenance during the planning session.