Automate BotNexus squad lifecycle management with deterministic naming and state merging.
npx skills add https://github.com/sytone/botnexus --skill squad-lifecycle
Please help me install this Agent Skill. Skill: squad-lifecycle Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/squad-lifecycle Command: npx skills add https://github.com/sytone/botnexus --skill squad-lifecycle
The Squad Lifecycle skill automates the end-to-end process of initializing, casting, and managing BotNexus squads, ensuring consistent setup and governance across repositories.
Initiate Init Mode to propose a squad roster and wait for user confirmation before creating the .squad structure.
High-intent search queries and answers about installing and using this skill.
To automate squad setup and team member casting, initiate Init Mode to propose and validate a roster, then apply deterministic naming and state merging rules to generate the .squad directory structure. This ensures consistent casting state and routing across branches.
The best way to migrate legacy squads is to use the migration workflow to join or retire agents while maintaining routing and decision logs. It enforces append-only history via history.json to ensure smooth collaboration and preserve state integrity.
The .squad directory convention ensures deterministic team management by enforcing policy.json and roster templates. It governs state merging rules, artifact formats, and registry.json to maintain consistent casting state and domain mappings.
Yes, you can validate a squad roster before files are created by using Init Mode. It proposes the roster and waits for user confirmation, preserving user intent before initializing the .squad structure and applying orchestration pipelines.
You do not need to manually update registry.json when adding or removing team members. The squad lifecycle process automatically maintains casting state, domain mappings, and history.json through deterministic assignment and append-only logging.
Squad state falls out of sync across branches when integration governance is not enforced. Applying roster headers and orchestration pipelines ensures that squad state and workflow routing remain consistently synchronized across all branches.
lbouriezPropose a squad roster and await user confirmation before initializing the .squad structure.
AratKruglikGenerate GitHub Actions workflows for automated testing, building, and deployment.
sachinnair90Propose a project team roster and create squad structure after explicit approval.
tae2089Audit agent-team runs, messages, events, and inboxes non-destructively.
