nexus-worker

Claim and complete Nexus CLI subtasks with parent plan awareness.

2|Updated Jun 29, 2021
One-click install
npx skills add https://github.com/pypeaday/dotfiles --skill nexus-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus-worker
Source: https://github.com/pypeaday/dotfiles/tree/main/opencode/.config/opencode/skill/nexus-worker
Command: npx skills add https://github.com/pypeaday/dotfiles --skill nexus-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nexus workers struggle to reliably claim and complete delegated subtasks while respecting parent plans and project context. This skill provides a structured workflow to autonomously manage nexus subtasks end-to-end, from claim to completion, with clear guidance and guardrails.

Core Features & Use Cases

  • Subtask Claim & Completion: Claim assigned subtasks and implement required changes.
  • Plan Awareness: Read parent plans and respect readiness constraints to avoid blocked work.
  • Context Loading: Load project and task context from delegation prompts to guide execution.

Quick Start

Load this skill to claim the subtask using the nexus CLI, inspect details, and complete the work by updating the subtask status.

Frequently Asked Questions about nexus-worker

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

FAQPage Schema
How do I automate claiming and completing delegated subtasks using a CLI workflow?

To automate subtask claiming and completion, you can use a structured CLI workflow to load delegation context, read subtask details, and update the subtask status. This ensures autonomous end-to-end management of delegated tasks.

What is a nexus worker and how does it manage delegated subtasks?

A nexus worker is an autonomous role that claims and completes delegated subtasks. It operates by loading project context and applying plan-awareness checks to ensure assigned work is executed reliably within a defined orchestration.

How do I check parent plan readiness before starting work on a claimed subtask?

You check parent plan readiness by inspecting the parent plan constraints before executing subtask work. This plan-awareness step prevents starting on blocked tasks and ensures the subtask is ready for implementation.

Do I need the Nexus CLI to load delegation context for automated issue management?

Yes, the Nexus CLI is required to load delegation context. The workflow depends on CLI-based interactions to read subtask details and load project context using the NEXUS_PROJECT environment variable.

What is the best way to handle blocked subtasks in an automated CLI workflow?

The best way to handle blocked subtasks is to escalate them when necessary within the defined orchestration. This ensures that readiness constraints are respected and blocked work is communicated properly.

Can I use prompt context to guide autonomous subtask execution across different projects?

Yes, you can operate with provided prompt context to guide execution across projects. The skill loads project and task context from delegation prompts to direct the autonomous completion of subtasks.