init-mode

Propose agent roles and create a standardized .squad directory structure.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Quintenps/contactswap-agents --skill init-mode-quintenps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/Quintenps/contactswap-agents/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/Quintenps/contactswap-agents --skill init-mode-quintenps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manual project initialization by automating team structure creation, agent role assignment, and repository configuration.

Core Features & Use Cases

  • Casting & Persistent Naming: Automatically assigns specialized AI agent roles based on project requirements and custom universes.
  • Standardized Structure: Enforces a consistent .squad directory layout, ensuring all team members and workflows are correctly initialized.
  • Conflict-Free Merging: Configures git attributes to enable seamless, append-only collaboration across branches for logs and decisions.

Quick Start

Activate the init-mode skill to propose a team and initialize the project structure for your new repository.

Frequently Asked Questions about init-mode

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

FAQPage Schema
How do I automate AI agent role assignment and project initialization?

Automated project initialization proposes specialized AI agent roles based on custom universes and configures a standardized directory layout to eliminate manual team setup friction.

How does agent-based collaboration manage persistent state across branches?

Agent-based collaboration manages persistent state by enforcing a consistent directory layout and configuring git attributes to enable conflict-free, append-only merging for logs and decisions.

Do I need predefined squad templates and git configuration access for project team setup?

Project team setup requires predefined squad templates and git configuration access to ensure consistent team composition, standardized directory creation, and seamless workflow integration.

What is the best way to structure a new software repository for agent-based collaboration?

The best way to structure a repository for agent-based collaboration is enforcing a standardized directory layout that initializes all team members and workflows consistently from the start.

Can I configure git attributes for conflict-free merging of logs and decisions?

Configuring git attributes for conflict-free merging allows append-only collaboration across branches, ensuring logs and decisions integrate seamlessly without manual merge conflicts.

Why does project team orchestration require predefined squad templates?

Project team orchestration requires predefined squad templates to guarantee consistent team composition and ensure new repository initialization aligns correctly with workflow integration standards.