Multi-agent engineering coordination system. Provides background knowledge about the Nexus architecture, workflow lifecycle, and CLI tooling. Auto-loads when .nexus.json exists in the project root. Not directly invocable — use the action skills instead.
Nexus coordinates multiple engineers and AI agents working on the same codebase. It tracks features, claims file paths to prevent conflicts, manages sessions with heartbeats, and preserves learnings and decisions across agent sessions.
The CLI (nexus) is the primary interface. The server (Hono.js + Bun) provides
the REST API and WebSocket for real-time updates. Redis handles file claims and
session heartbeats. PostgreSQL (via Drizzle ORM) stores persistent state.
Check for .nexus.json in the project root. If it exists, the project is linked.
{
"projectId": "uuid",
"projectName": "My Project",
"projectSlug": "my-project",
"linkedAt": "2025-01-01T00:00:00Z",
"activeFeature": "feature-slug" // present when a feature is picked
}
If activeFeature is set, the engineer is actively working on that feature.
Read for the feature specification.
.nexus/active/<slug>/spec.mddraft ──> ready ──> in_progress ──> done
↑ │
└── release ─┘
nexus feature availableOnly one engineer can hold a feature at a time. Picking a feature locks its
touches file paths in Redis. Releasing or completing returns the feature to
the pool and releases all claims.
Features are organized into lanes: icebox < later < next < now.
Within each lane, features are sorted by priority number.
| Skill | Slash Command | Purpose |
|---|---|---|
| available | /available | See claimable features |
| pick | /pick <slug> | Claim a feature and export spec |
| done | /done | Mark feature complete |
| learn | /learn <insight> | Record a learning |
| decision | /decision <what> | Record an architectural decision |
| save | /save <message> | Save a progress checkpoint |
| status | /status | Show project status overview |
| roadmap | /roadmap | View features by priority lane |
When working in a Nexus project with an active feature:
/learn./decision./save./done — but always ask the user first..nexus.json for activeFeature before suggesting pick