Initialize a missing `.squad/team.md` via a two-phase proposal and creation workflow.
npx skills add https://github.com/elbruno/md-to-slides --skill init-mode-elbruno
Please help me install this Agent Skill. Skill: init-mode Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/init-mode Command: npx skills add https://github.com/elbruno/md-to-slides --skill init-mode-elbruno
It prevents premature repo/team file creation by orchestrating a two-phase team initialization that first proposes roles for confirmation, then only creates the required .squad/ structure after approval.
git config user.name, proposes a cast (with a casting and persistent naming algorithm), and uses ask_user to confirm the roster before touching the filesystem..squad/ directories, initializes casting state files (policy.json, registry.json, history.json), seeds agent context, and enforces team.md with the required ## Members header for workflow compatibility..gitattributes merge rules for append-only .squad/ files to reduce conflicts across branches..squad/team.md exists yet—this skill quickly turns a high-level project description into a ready team structure without risking accidental changes before the user approves.Use init-mode to initialize .squad/ by first proposing a team roster and then, after you confirm, creating the full project team structure.
High-intent search queries and answers about installing and using this skill.
Team initialization can be orchestrated safely by first proposing a role cast for user confirmation via an interactive prompt, and only creating the `.squad/` directory structure after explicit approval is granted. This prevents premature repository file creation.
Bootstrapping a squad framework safely involves a two-phase workflow: proposing team roles based on the git user name, then creating required state files like `policy.json` and `registry.json` only after the roster is confirmed. This ensures controlled project setup.
To set up merge-safe agent state files, initialize the `.squad/` directory and add `.gitattributes` merge rules for append-only files. This reduces cross-branch merge conflicts when team history and registry files are updated.
Yes, a git user name is required for project bootstrapping. The initialization workflow runs `git config user.name` to identify the user and propose a cast-based team roster, which you must confirm before any filesystem changes occur.
Yes, this initialization approach creates a `team.md` file within the `.squad/` directory and automatically enforces the required `## Members` header. This ensures immediate compatibility with downstream squad framework workflows.
jonnymuirInitialize project team roles and .squad directory structure in a repository.
dotnetPropose cast roles and scaffold .squad structure after user confirmation.
NicolasPadovamOrchestrate multi-agent workflows with squad definitions and configuration files.
bradygasterPropose an AI development team roster and await confirmation before generating team.md and gitattributes.