Strategy nexus
163 specialist Claude Code agents + 24 routing skills + 16 strategy playbooks. Korean/Japanese Business Navigators, game-dev (Unity/Unreal/Godot/Roblox/Blender), XR/spatial, paid-media routing. skill-routing-arbitrator disambiguates the ~500-skill ecosystem. Fork of msitarzewski/agency-agents.
npx -y skills add daehounan/agency-agents-fork --skill strategy-nexusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
NEXUS multi-agent orchestration playbook for end-to-end strategic engagements. Use when the user wants to orchestrate a full agency-style engagement across multiple specialists, run a phased strategic project (discovery → strategy → foundation → build → hardening → launch → operate), execute one of the named scenarios (startup MVP, enterprise feature, marketing campaign, incident response), or apply quality gates and handoff protocols across an entire team of agents. Triggers on NEXUS, multi-agent orchestration, agency engagement, phased strategic project, discovery phase, hardening phase, MVP launch, enterprise feature shipping, agent coordination matrix, quality gate, handoff protocol.
SKILL.md
2.5 KB, as published. Nobody here has run it
NEXUS Strategy Orchestration Skill
When this skill activates, route the user to the appropriate NEXUS playbook based on engagement type and phase.
Top-level entry points
| User signal | Playbook to load |
|---|---|
| "Where do I start?" / "how do I run an engagement?" | strategy/QUICKSTART.md |
| "Give me the executive view" | strategy/EXECUTIVE-BRIEF.md |
| "Walk me through the full doctrine" | strategy/nexus-strategy.md |
Phase playbooks (sequential)
| Phase | Focus | Playbook |
|---|---|---|
| 0 | Intelligence & Discovery | strategy/playbooks/phase-0-discovery.md |
| 1 | Strategy & Architecture | strategy/playbooks/phase-1-strategy.md |
| 2 | Foundation & Scaffolding | strategy/playbooks/phase-2-foundation.md |
| 3 | Build & Iterate | strategy/playbooks/phase-3-build.md |
| 4 | Quality & Hardening | strategy/playbooks/phase-4-hardening.md |
| 5 | Launch & Growth | strategy/playbooks/phase-5-launch.md |
| 6 | Operate & Evolve | strategy/playbooks/phase-6-operate.md |
Named scenarios (cross-phase)
| Scenario | Runbook |
|---|---|
| Startup MVP shipping | strategy/runbooks/scenario-startup-mvp.md |
| Enterprise feature delivery | strategy/runbooks/scenario-enterprise-feature.md |
| Marketing campaign launch | strategy/runbooks/scenario-marketing-campaign.md |
| Production incident response | strategy/runbooks/scenario-incident-response.md |
Coordination assets
- Agent activation prompts:
strategy/coordination/agent-activation-prompts.md - Handoff templates:
strategy/coordination/handoff-templates.md
When NOT to use
- Single-agent task → call the agent directly
- Tactical question (one phase only) → load that one phase playbook
- Lightweight planning → use
ecc:plannerorecc:planinstead