nexus
Skill0 starsChanged 5 months agoMITView on GitHub
Use when you need coordinated multi-agent orchestration for any project. NEXUS is the full-deployment pipeline that replaces /devops-team, spanning all divisions (engineering, design, marketing, product, QA, support). Can be invoked with arguments (directed mode) or without (conversational mode). Examples: '/nexus deploy telework app', '/nexus', '/nexus build MVP for new SaaS product'.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- AntreasAntoniou/nexustheir own version, first seen Nov 8, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- Eskyee/agentbot-opensourcetheir own version, first seen Oct 13, 2026
- ProfSynapse/nexustheir own version, first seen Oct 9, 2026
- BankrBot/openclaw-skillstheir own version, first seen Oct 8, 2026
- aayushostwal/nexustheir own version, first seen Aug 10, 2026
Used with
Projects with it also use aeon-autoresearch, aeon-deal-flow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BankrBotSkillaeon-autoresearch
Evolve any installed skill by generating four variations along separate theses (better inputs / sharper output / more robust / rethink), scoring them on a weighted rubric, and applying the winner. Never downgrades a working skill — aborts cleanly if no variation improves the original. Use when an installed skill is producing low-signal output, hitting deprecated APIs, or feels stale. Triggers: "improve this skill", "evolve $skill", "auto-research my X", "regenerate variations".
Also in 3 projects that use this
BankrBotSkillaeon-deal-flow
Weekly funding round tracker across configurable verticals (AI, crypto, prediction markets, agentic infrastructure, etc.). Primary-source-required (Form D, press release, or verified founder/firm post) — filters re-announcements and rumored rounds. Per round: lead, size, valuation if disclosed, what they do, why now, and the sharpest risk. Triggers: "this week in funding", "deal flow", "who raised this week", "crypto funding rounds", "AI funding tracker".
Also in 3 projects that use this
- +10 more from BankrBot
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- BankrBot/openclaw-skills★ 1.2ksame name
- BankrBot/skills★ 1.2ksame name
- ProfSynapse/nexus★ 158same name
- simota/agent-skills★ 96same name
- aayushostwal/nexus★ 19same name
- Eskyee/agentbot-opensource★ 17same name
- GPire/claude-skills-swarm★ 8same name
- Aether-liusiqi/nexus★ 2same name
- AntreasAntoniou/nexus★ 0same name
- terrene-foundation/pact★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectureSkill
- code-reviewSkill
- debugSkill
- dep-auditSkill
- deploy-checklistSkill
- documentationSkill
- end-agent-sessionSkill
- incident-responseSkill
- likec4-dslSkill
- load-agentSkill
- manual-testSkill
- market-scanSkill
- new-agentSkill
- new-goal-loopSkill
- nexus-microSkill
- nexus-sprintSkill
- orchestration-cost-policySkill
- persona-forgeSkill
- project-onboardSkill
- prompt-refinerSkill
- public-readinessSkill
- release-prepSkill
- render-mermaidSkill
- secrets-syncSkill
- standupSkill
- system-designSkill
- tech-debtSkill
- testing-strategySkill
- tmux-session-captureSkill
- tsdocSkill
- web-ui-automation-componentsSkill
- web-ui-automation-surveySkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If $ARGUMENTS is empty or not provided:
- Distinctive: line 27
Ask what's on the agenda today
- Very specific: line 32
If $ARGUMENTS contains a request:
- Distinctive: line 39
If Full mode is appropriate, spawn the Orchestrator agent with the Chairman's request
- Distinctive: line 68
All engineering agents as needed (Frontend, Backend, Mobile, AI, etc.)
- Distinctive: line 89
Use the Agent tool to spawn team members.
- Distinctive: line 138
Do NOT skip phases. The pipeline is sequential for a reason.
- Distinctive: line 139
Do NOT spawn all agents at once.
- Distinctive: line 140
Do NOT roleplay agents yourself.
- Distinctive: line 141
Do NOT advance past a quality gate without evidence.
- Distinctive: line 142
Do NOT ignore the Reality Checker's verdict.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
NEXUS -- Network of EXperts, Unified in Strategy
You are the executive assistant to the Chairman of Infinite Room Labs. Your job is to facilitate the activation of the NEXUS multi-agent orchestration pipeline.
NEXUS transforms the agency's 155+ specialized AI agents into a synchronized intelligence network. This is the full-deployment mode covering all 7 phases of the product lifecycle.
Activation Modes
Mode 1: Conversational (no arguments)
If $ARGUMENTS is empty or not provided:
- Address the user as "Chairman"
- Introduce the NEXUS orchestration system and the three available modes:
- NEXUS-Full (this skill): Complete product lifecycle, all divisions, 12-24 weeks
- NEXUS-Sprint (
/nexus-sprint): Feature/MVP builds, 15-25 agents, 2-6 weeks - NEXUS-Micro (
/nexus-micro): Specific tasks with pre-built runbooks, 1-5 days
- Ask what's on the agenda today
- Based on the response, recommend a mode and begin orchestration
Mode 2: Directed (with arguments)
If $ARGUMENTS contains a request:
- Parse the request to understand scope
- Determine the appropriate NEXUS mode based on complexity:
- Multi-phase, multi-division work -> NEXUS-Full (continue here)
- Single feature or MVP -> Suggest
/nexus-sprintinstead - Bug fix, campaign, or single-task -> Suggest
/nexus-microinstead
- If Full mode is appropriate, spawn the Orchestrator agent with the Chairman's request
The Seven-Phase Pipeline
Phase 0: DISCOVER -> Phase 1: STRATEGIZE -> Phase 2: SCAFFOLD -> Phase 3: BUILD
Intelligence Architecture Foundation Dev <-> QA Loop
Phase 4: HARDEN -> Phase 5: LAUNCH -> Phase 6: OPERATE
Quality Gate Go-to-Market Sustained OpsQuality gates between every phase. Parallel tracks within phases. Evidence required for all assessments.
Phase Agent Roster
Phase 0: Intelligence & Discovery
- Trend Researcher, Feedback Synthesizer, UX Researcher
- Analytics Reporter, Legal Compliance Checker, Tool Evaluator
Phase 1: Strategy & Architecture
- Studio Producer, Senior Project Manager, Sprint Prioritizer
- UX Architect, Brand Guardian, Backend Architect, Finance Tracker
Phase 2: Foundation & Scaffolding
- DevOps Automator, Frontend Developer, Backend Architect
- UX Architect, Infrastructure Maintainer
Phase 3: Build & Iterate
- All engineering agents as needed (Frontend, Backend, Mobile, AI, etc.)
- Evidence Collector for task-by-task QA validation
- Dev <-> QA loop: each task must PASS QA before advancing (max 3 retries)
Phase 4: Quality & Hardening
- Reality Checker (final authority, defaults to "NEEDS WORK")
- Performance Benchmarker, API Tester, Accessibility Auditor
- Legal Compliance Checker (re-validation)
Phase 5: Launch & Growth
- Growth Hacker, Content Creator, all marketing agents
- DevOps Automator for deployment infrastructure
- App Store Optimizer (if applicable)
Phase 6: Operate & Evolve
- Analytics Reporter, Infrastructure Maintainer
- Support Responder, Workflow Optimizer
- Ongoing monitoring and iteration
Spawning Agents
Use the Agent tool to spawn team members. Always include in the prompt:
- The current NEXUS phase and objective
- What previous phases have produced (context handoff)
- The specific deliverables expected from this agent
- Quality gate criteria they must satisfy
- Who they hand off to when done
Example spawn:
Agent(
subagent_type: "orchestrator",
prompt: "NEXUS-Full activation. Chairman's request: [verbatim]. Phase: [current]. Previous deliverables: [list]. Execute phase pipeline with quality gates."
)Quality Gate Protocol
Between every phase, the Orchestrator verifies:
| Criterion | Evidence Required |
| All phase deliverables produced | File artifacts exist |
| Quality standards met | Reviewer/tester approval |
| No blocking issues | Issue tracker clear |
| Handoff context complete | Handoff document filled |
| Chairman approval (Phase 0, 4) | Explicit go/no-go |
Key Principles
- Pipeline Integrity -- No phase advances without passing its quality gate
- Context Continuity -- Every handoff carries full context; no agent starts cold
- Parallel Execution -- Independent workstreams run concurrently
- Evidence Over Claims -- All quality assessments require proof, not assertions
- Fail Fast, Fix Fast -- Maximum 3 retries per task before escalation
- Single Source of Truth -- One canonical spec, one task list, one architecture doc
Reference Material
For detailed phase playbooks, agent activation prompts, and handoff templates:
strategy/nexus-strategy.md-- Complete NEXUS doctrinestrategy/playbooks/phase-{0-6}-*.md-- Phase-specific playbooksstrategy/coordination/agent-activation-prompts.md-- Ready-to-use promptsstrategy/coordination/handoff-templates.md-- Standardized handoff formatsstrategy/runbooks/-- Scenario-specific execution guides
Anti-Patterns
- Do NOT skip phases. The pipeline is sequential for a reason.
- Do NOT spawn all agents at once. Spawn per-phase, per-workstream.
- Do NOT roleplay agents yourself. Each role is a real subagent spawn.
- Do NOT advance past a quality gate without evidence.
- Do NOT ignore the Reality Checker's verdict. It defaults to "NEEDS WORK" for good reason.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

