nexus-workflows

Orchestrate feature development workflows from planning through review and completion.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/houke/nexus --skill nexus-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus-workflows
Source: https://github.com/houke/nexus/tree/main/skills/nexus-workflows
Command: npx skills add https://github.com/houke/nexus --skill nexus-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software development teams struggle with disconnected planning, execution, and review phases that lead to documentation drift, lost context, and inconsistent delivery. This Skill provides a unified orchestration system that keeps feature lifecycle artifacts synchronized and enforces quality gates.

Core Features & Use Cases

  • Multi-Phase Workflows: Structured planning, execution, review, sync, summary, hotfix, and initialization workflows managed via slash commands or natural language triggers.
  • Parallel Orchestration: Coordinates multiple specialized agents in parallel waves with dependency-aware scheduling and concurrency limits.
  • Traceability & Safety: Maintains feature folders with plan, execution, and review documents; enforces non-interactive commands, protects critical directories, and requires QA and Tech-Lead sign-offs.

Quick Start

Use the nexus-workflows skill to plan and execute a new user authentication feature by invoking the /nexus-workflows plan and /nexus-workflows execute slash commands in sequence.

Frequently Asked Questions about nexus-workflows

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

FAQPage Schema
How do I orchestrate multi-agent software feature development workflows?

Multi-agent software feature development workflows are orchestrated by coordinating specialized agents in parallel waves with dependency-aware scheduling and concurrency limits to execute structured planning, code review, and documentation synchronization phases.

What is the best way to keep feature lifecycle artifacts synchronized during parallel execution?

Feature lifecycle artifacts are kept synchronized by maintaining feature folders containing plan, execution, and review documents within a dedicated .nexus/ directory, ensuring documentation drift is prevented across all development phases.

Does this workflow orchestration system enforce code review and quality gates?

The workflow orchestration system enforces quality gates by requiring explicit QA and Tech-Lead sign-offs, protecting critical directories, and mandating non-interactive commands during the review phase before feature completion.

Do I need a specific directory structure to manage multi-agent project status tracking?

A specific directory structure is required to manage project status tracking, necessitating a .nexus/ directory containing feature folders, an AGENTS.md file, and agent memory files to manage workflow state and traceability.

How do I plan and execute a feature lifecycle from start to finish?

You plan and execute a feature lifecycle by sequentially invoking the plan and execute slash commands or natural language triggers, moving structured workflows through planning, execution, review, sync, and summary phases.

When should I use a structured feature lifecycle workflow over ad-hoc development?

A structured feature lifecycle workflow should be used over ad-hoc development when multi-agent environments require dependency-aware parallel execution, strict traceability, and enforced quality sign-offs to prevent lost context and inconsistent delivery.