Creates a team roster and configures .gitattributes after user confirmation.
npx skills add https://github.com/usepowershell/PoshMcp --skill init-mode-usepowershell
Please help me install this Agent Skill. Skill: init-mode Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/init-mode Command: npx skills add https://github.com/usepowershell/PoshMcp --skill init-mode-usepowershell
Init Mode solves the problem of safely bootstrapping a project team when no squad roster exists by proposing a cast, collecting explicit user confirmation, and only creating repository state after approval to prevent premature or unwanted writes.
## Members header required by downstream automation.Ask the coordinator to propose a four-person engineering team for a TypeScript CLI and present a selectable confirmation menu.
High-intent search queries and answers about installing and using this skill.
To safely initialize team onboarding, a casting algorithm proposes a roster and presents a selectable menu, delaying file creation until explicit confirmation to prevent unwanted repository writes.
The best way to set up a .squad directory is confirming a proposed team roster, which seeds agent folders, creates a casting registry, and updates .gitattributes with union merge rules to support multi-branch collaboration.
Automated team initialization does not store git user.email. It reads git user.name for personalization while explicitly avoiding email collection to prevent PII leakage during the squad setup process.
Yes, an AI coordinator can propose a 4-person engineering team for a TypeScript CLI. It iterates on roles with you via a selectable confirmation menu before initializing the squad directory and merge-driver settings.
Team initialization requires the exact ## Members header in team.md because downstream automation relies on this specific format to correctly parse the team roster and execute subsequent workflow tasks.
You need to configure append-only union merge rules in .gitattributes when initializing a .squad directory for multi-branch collaboration, ensuring concurrent agent history updates do not conflict during repository merges.
dotnetPropose cast roles and scaffold .squad structure after user confirmation.
nirholasManage XActions teams and member roles through API endpoints.
MelvynxAutomate Git branch merges with context-aware conflict resolution.
Leep-GHPropose a project roster and create the team structure after user confirmation.