skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

init-mode

Propose cast roles and scaffold .squad structure after user confirmation.

209|27|Updated Mar 10, 2026
Search Tags:#orchestration#team initialization#repo scaffolding#merge safety#roster confirmation#persistent naming#casting system
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill init-mode-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/init-mode
Command: npx skills add https://github.com/dotnet/maui-labs --skill init-mode-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

init-mode prevents wasted setup effort by guiding you through a two-phase team initialization: first proposing roles for your coordination space, then creating the required .squad/ structure only after you explicitly confirm.

Core Features & Use Cases

  • Two-phase, confirmation-gated initialization: Proposes a team roster (including cast/universe selection) without creating any files until the user confirms.
  • Persistent naming & casting-state bootstrapping: Initializes casting policy, registries, and assignment history so future steps have stable team identity.
  • Repo-safe, workflow-compatible structure: Ensures team.md includes the required ## Members header and sets up conflict-free merge drivers for append-only .squad/ state.

Quick Start

Run init-mode by triggering it in the repo when .squad/team.md is missing or has no roster members, then answer the roster confirmation prompt to generate the team scaffold.

Frequently Asked Questions about init-mode

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

FAQPage Schema
How do I initialize a project team roster without creating files prematurely?▼

Team initialization uses a two-phase, confirmation-gated process that proposes cast roles and roster adjustments first, only scaffolding the `.squad/` structure after explicit user confirmation.

What is the required structure for a coordination repository team.md file?▼

The team.md file requires a hard-coded `## Members` header to ensure workflow compatibility and establish a stable team identity for future orchestration steps.

Can I iteratively adjust cast roles before finalizing repo scaffolding?▼

Yes, you can add or change cast roles iteratively during the proposal phase before creation, allowing roster adjustments until you explicitly confirm the final team structure.

How does merge safety work for append-only state files in a team workspace?▼

Merge safety is enforced by configuring union merge drivers for append-only `.squad/` state files, preventing conflicts while maintaining persistent casting policy and assignment history.

When should I trigger team initialization in a new-workspace orchestration?▼

Trigger initialization when `.squad/team.md` is absent or empty, which prompts the system to propose a roster and bootstrap persistent naming and casting-state registries.

Related Skills

Explore More Product & Management Skills→
elbrunoelbruno
2

init-mode

Initialize a missing `.squad/team.md` via a two-phase proposal and creation workflow.

Community
Advanced
balamurubalamuru

project-scaffolder

Create isolated project directories with boilerplate and task artifacts.

Community
Intermediate
hirokazu-kobayashi-koba-hirohirokazu-kobayashi-koba-hiro
7

user-management

Manage user lifecycles, identity policies, and password controls for multi-tenant environments.

Community
Advanced
DeDuvaDeDuva
1

init-mode

Propose a team roster and create a .squad directory after user confirmation.

Community
Advanced