project-conductor

Coordinate cross-functional teams through the NEXUS 7-Phase Pipeline.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jc180105/.opencode --skill project-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conductor
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/project-conductor
Command: npx skills add https://github.com/jc180105/.opencode --skill project-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides end-to-end orchestration of large, multi-team projects using the NEXUS 7-Phase Pipeline, ensuring consistent execution, traceability, and seamless agent handoffs.

Core Features & Use Cases

  • Central orchestration via the Project Conductor to assign roles, coordinate phases, and enforce quality gates.
  • Activation in three modes (NEXUS-Full, NEXUS-Sprint, NEXUS-Micro) and template-driven workflow invocation for repeatable patterns.
  • MCP Memory integration for cross-agent context sharing and Progress skill for per-phase progress persistence.

Quick Start

Provide your project goal and activate Project Conductor to run the full NEXUS pipeline with memory enabled, and ensure progress is saved after each phase.

Frequently Asked Questions about project-conductor

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

FAQPage Schema
How do I orchestrate cross-functional teams for complex project management?

You can orchestrate complex project management by assigning explicit agent roles and coordinating phase-by-phase execution through a 7-Phase Pipeline. This ensures consistent execution, traceability, and seamless agent handoffs across multiple teams.

Can I scale project coordination from a targeted task to a full from-scratch build?

Yes, project coordination scales from micro to full-project engagements using three activation modes: NEXUS-Full for from-scratch builds, NEXUS-Sprint for feature MVPs, and NEXUS-Micro for targeted task work.

How does MCP memory integration work for cross-agent context sharing?

MCP memory integration provides a back-channeling mechanism for cross-agent context sharing. It persists per-phase progress so that context is maintained and traceable across different agents throughout the pipeline execution.

What is the best way to ensure consistent execution and quality across multi-team projects?

The best way to ensure consistent execution is using a central Project Conductor to assign roles, coordinate phases, and enforce quality gates. This is supplemented by template-driven workflow invocation for repeatable patterns.

Do I need explicit agent roles to run the NEXUS pipeline?

Yes, explicit agent roles are required to coordinate cross-functional teams. The pipeline enforces phase-by-phase execution and quality gates that depend on clearly defined agent responsibilities and seamless handoffs.

When should I not use template-driven workflow invocation for project orchestration?

Template-driven workflow invocation is designed for repeatable project patterns. You should avoid it when your project requires highly bespoke, non-repeatable workflows that cannot be standardized into a template structure.