nexus-orchestrator

To decompose project epics into subtasks and delegate them, claim the high-level issue, create a plan for approval, then use nexus issue create with a parent ID to generate subtasks and delegate them to worker subagents for execution.

A plan-first workflow for project orchestration requires creating a plan and obtaining human approval before any feature work begins, ensuring a readiness gate is passed so subtasks can only be claimed after the plan is explicitly approved.

Delegating work to subagents improves project management by enforcing standardized context and ownership, ensuring reproducible workflows across teams while maintaining alignment through monitoring and updating tasks with CLI commands.

Yes, you can use the Nexus CLI to monitor delegated subtasks by running nexus issue list with the parent ID to track progress and maintain alignment across the decomposed project work.

Yes, you need human approval before claiming feature subtasks because the orchestration enforces a readiness gate, requiring you to create a plan, present it for approval, and set it to ready before subtasks can be claimed.

You handle project context discovery for Nexus orchestration by using the environment state and repository name, enabling the system to automatically select the correct Nexus project for your workflow.