init-mode

Propose and initialize team structures with rosters and .squad casting state.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill init-mode-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/quaid-app/quaid --skill init-mode-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Team onboarding and orchestration can be error-prone and slow when starting new projects. init-mode provides a guided flow that proposes an initial team roster (Phase 1) and, after confirmation, creates the team structure and casting state (Phase 2).

Core Features & Use Cases

  • Phase 1: Propose the Team: Detect lack of roster and propose a task-specific, role-aware team; use git config user.name to personalize dialogue and avoid using user.email. Use ask_user to confirm roster choices with a menu of options.
  • Phase 2: Create the Team: Upon confirmation, initialize .squad structure (team.md, routing, etc.), seed agents' history with project context, and prepare casting state for ongoing collaboration.
  • Use Case: When starting a new project, automatically bootstrap team roles and project scaffolding to accelerate onboarding and alignment.

Quick Start

Ask your AI to begin the init-mode workflow to propose a team and create the .squad structure after confirmation.

Frequently Asked Questions about init-mode

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

FAQPage Schema
How do I bootstrap a project team roster and initialize the squad structure?

To bootstrap a project team roster, the init-mode workflow proposes a role-aware team in Phase 1, then upon user confirmation, creates the .squad structure and seeds agent histories in Phase 2.

What is the best way to automate team onboarding and project scaffolding for a new squad?

Automating team onboarding requires a guided initialization flow that proposes task-specific roles, confirms choices via an ask_user menu, and then generates team infrastructure and routing rules.

Can I personalize the team setup dialogue using git config without exposing my email?

Yes, team setup dialogue can be personalized by reading git config user.name directly, deliberately avoiding the use of user.email to maintain privacy during the initialization workflow.

How does the two-phase team initialization process work for project setup?

The two-phase team initialization works by first proposing a roster for user confirmation, then creating the team structure, seeding project context into agent histories, and preparing casting state for collaboration.

When do I need to initialize frontmatter metadata and casting state for a new project?

You need to initialize frontmatter metadata and casting state when no roster exists or when a Phase 1 proposal is required, ensuring the .squad infrastructure is properly configured for ongoing orchestration.

What files and configurations are created during the squad team setup phase?

During the squad team setup phase, the workflow initializes the .squad directory structure, generates team.md, configures routing rules, seeds agent histories, and records initialization decisions.