init-mode

Generate and validate a .squad structure with initial casting for new projects.

413|64|Updated Feb 7, 2023

Search Tags:#automation #orchestration #roster #project-setup #team #squad #casting

Ready to run

npx skills add https://github.com/christianhelle/refitter --skill init-mode-christianhelle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/christianhelle/refitter/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/christianhelle/refitter --skill init-mode-christianhelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the initial team setup and project governance by generating a persistent .squad structure, casting decisions, and agent histories for a new project.

Core Features & Use Cases

Proposes an initial roster when no .squad/team.md exists and awaits explicit user confirmation.
Creates and seeds the .squad state, including casting policy, registry, and agent histories to enable continuity across sessions.
Supports Phase 1 proposal and Phase 2 creation with structured prompts and automation, including safe handling of project context.

Quick Start

If no .squad/team.md exists, start Phase 1 by proposing a team roster and waiting for user confirmation.

Frequently Asked Questions about init-mode

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

FAQPage Schema

How do I automate initial squad setup and team roster casting for a new project?▼

Automate initial squad setup by generating and validating a persistent .squad structure, including casting decisions and agent histories. The process proposes a team roster, awaits user confirmation, and seeds the registry to enable traceable collaboration across sessions.

What is squad initialization and when do I need it for project governance?▼

Squad initialization coordinates team setup and project governance by generating a persistent .squad structure. You need it during Phase 1 proposal and Phase 2 creation to establish casting policies, registries, and agent histories for new projects.

How do I create a persistent .squad state with casting policy and agent histories?▼

Create the .squad state through structured Phase 2 creation automation. This seeds the casting policy, registry, and agent histories, ensuring continuity and traceable collaboration across multiple sessions without losing squad context.

Do I need to confirm the team roster proposal before project setup begins?▼

Yes, you must confirm the team roster proposal. When no .squad/team.md file exists, the system proposes an initial roster in Phase 1 and explicitly awaits your confirmation via user interaction before proceeding with project creation.

What's the best way to ensure traceable collaboration across sessions for a new squad?▼

Ensure traceable collaboration by seeding the .squad registry and agent histories during initialization. This persistent state structure enables continuity across sessions, safely handling project context and recording casting decisions.

Are there limitations to the automated team initialization process?▼

The automated team initialization requires explicit user confirmation before applying roster proposals. It is designed specifically for Phase 1 proposal and Phase 2 creation, meaning it handles initial setup rather than ongoing squad management or modifications.