Nexus Strategy

Orchestrates multi-agent workflows across seven project lifecycle phases with quality gates.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill nexus-strategy-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Nexus Strategy
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/strategy/nexus-strategy
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill nexus-strategy-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating many independent AI specialist agents on a single project leads to conflicting decisions, duplicated effort, and quality gaps at handoff boundaries. This Skill provides a deployment doctrine that synchronizes agents into a structured pipeline with defined roles, handoffs, and quality gates. ## Core Features & Use Cases - Seven-Phase Pipeline: Defines Discover, Strategize, Scaffold, Build, Harden, Launch, and Operate phases, each with active agents, parallel workstreams, and quality gates. - Dev-QA Loop: Manages task-by-task implementation with evidence-based QA verdicts, a maximum of three retries, and escalation rules. - Coordination Matrix & Handoff Protocols: Maps cross-division dependencies and critical artifact handoffs between agents. - Use Case: When launching a new product, activate NEXUS-Full mode to run market research in Phase 0, architecture in Phase 1, scaffolding in Phase 2, iterative builds in Phase 3, hardening in Phase 4, and coordinated go-to-market in Phase 5. ## Quick Start Ask the agent to orchestrate a full product launch using the NEXUS pipeline starting with Phase 0 market intelligence.

Frequently Asked Questions about Nexus Strategy

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

FAQPage Schema
How do I coordinate multiple AI agents on one project?▼

Use a phased pipeline that assigns each agent a role, output artifact, and handoff target per phase. NEXUS defines seven phases from discovery to operations, with quality gates between phases and an orchestrator managing task-level Dev-QA loops.

What is the NEXUS multi-agent operating model?▼

NEXUS is a seven-phase pipeline (Discover, Strategize, Scaffold, Build, Harden, Launch, Operate) with three activation modes: NEXUS-Full for full lifecycles, NEXUS-Sprint for 2-6 week features, and NEXUS-Micro for 1-5 day tasks.

How does the Dev-QA loop handle failed tasks?▼

Each implemented task is tested by a QA agent such as the Evidence Collector. A PASS verdict advances to the next task, a FAIL triggers a retry with feedback up to three attempts, and persistent failures escalate to the orchestrator.

When should I use NEXUS-Micro instead of NEXUS-Full?▼

Use NEXUS-Micro with 5-10 agents for bug fixes, content campaigns, or single deliverables lasting 1-5 days. NEXUS-Full activates all agents for enterprise product launches spanning 12-24 weeks.

What are the limitations of a phase-gated agent pipeline?▼

Phase gates add overhead that can slow very small tasks, and the model assumes enough specialist agents exist to fill each division role. First implementations typically require 2-3 revision cycles at the Phase 4 hardening gate.