Quickstart

Orchestrates multi-agent pipelines using NEXUS modes with phase playbooks and quality gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating dozens of specialized AI agents one at a time leads to inconsistent handoffs and unverified work. This Skill provides a structured quick-start guide for the NEXUS framework, defining exactly which agents act, in what order, and how quality is verified at every phase. ## Core Features & Use Cases - Three Orchestration Modes: NEXUS-Full for complete products (12-24 weeks), NEXUS-Sprint for features or MVPs (2-6 weeks), and NEXUS-Micro for specific tasks (1-5 days). - Ready-to-Copy Activation Prompts: Pre-built prompts for scenarios like bug fixes, marketing campaigns, compliance audits, performance investigations, market research, and UX improvements. - Playbook & Runbook Index: Links to phase playbooks (discovery through operate), coordination templates, and scenario runbooks for startup MVPs, enterprise features, and incident response. - Use Case: A founder wants to build an MVP in four weeks. They copy the NEXUS-Sprint prompt, describe the feature, and the Agents Orchestrator runs architecture, Dev-QA loops, and Reality Checker approval before launch. ## Quick Start Activate the Agents Orchestrator in NEXUS-Sprint mode and describe the feature or MVP you want to build.

Frequently Asked Questions about Quickstart

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

FAQPage Schema
How do I orchestrate multiple AI agents for a project?▼

Use the NEXUS framework by activating the Agents Orchestrator in one of three modes: NEXUS-Full for complete products, NEXUS-Sprint for features or MVPs, or NEXUS-Micro for specific tasks. Each mode defines which agents participate and the phase sequence they follow.

What is the difference between NEXUS-Full, NEXUS-Sprint, and NEXUS-Micro?▼

NEXUS-Full runs all agents across seven phases over 12-24 weeks for complete products. NEXUS-Sprint uses 15-25 agents over 2-6 weeks for features, skipping market validation. NEXUS-Micro uses 5-10 agents over 1-5 days for single tasks like bug fixes or audits.

How do quality gates work in a multi-agent pipeline?▼

No phase advances without evidence-based approval at a quality gate. Every task runs through a Dev-QA loop where work is built then tested, with a maximum of three retries before escalation, and the Reality Checker agent holds final quality authority.

Can I use NEXUS for a single task like a bug fix or compliance audit?▼

Yes, NEXUS-Micro mode handles specific tasks with 5-10 agents in 1-5 days. Pre-built prompts cover bug fixes, marketing campaigns, compliance audits, performance investigations, market research, and UX improvements.

What are the limitations of the NEXUS orchestration approach?▼

NEXUS depends on the referenced strategy documents, playbooks, and runbooks existing in the strategy directory, and on the named specialist agents being available. Tasks requiring fewer than the minimum agent coordination may be faster handled by a single agent directly.