init-mode

Propose a team roster and create the .squad workspace after user confirmation.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill init-mode-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill init-mode-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps automate the initial setup of a new project by proposing a team roster when no team exists and awaiting explicit confirmation before proceeding to Phase 2 creation.

Core Features & Use Cases

  • Phase 1: Propose the team roster using a casting strategy and user prompts.
  • Phase 2: Create the .squad workspace, seed agent histories, and enable persistent logging with append-only merge rules for cross-branch workflows.
  • Use Case: A project kickoff where a coordinator defines a roster, confirms with the user, and automates the transition to a working squad setup.

Quick Start

Initiate a Phase 1 roster proposal and wait for user confirmation to proceed to Phase 2.

Frequently Asked Questions about init-mode

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

FAQPage Schema
How do I automate phased team initialization for a new project?

Phased team initialization proposes a roster using a casting strategy, prompts for user confirmation, and then creates the workspace structure. It coordinates setup by seeding agent histories and initializing state for day-1 context.

What is the best way to set up a project roster with user confirmation?

The best way to set up a project roster is through a two-phase process: Phase 1 proposes the team roster and awaits explicit user confirmation, while Phase 2 creates the .squad workspace and seeds agent histories.

How does phased team setup handle cross-branch workflows?

Phased team setup handles cross-branch workflows by enabling persistent logging with append-only merge rules. This ensures that workspace state and agent histories remain consistent across branches during initialization.

Do I need existing agent histories before starting team setup?

No, you do not need existing agent histories before starting team setup. The initialization process seeds agent histories automatically during Phase 2, providing day-1 context for the newly created squad workspace.

Can I use workflow orchestration to collect input during team setup?

Yes, workflow orchestration uses the ask_user tool to collect input during team setup. This prompts the user explicitly during Phase 1 to confirm the proposed roster before proceeding to workspace creation.

Why does team initialization require explicit user confirmation?

Team initialization requires explicit user confirmation to ensure the proposed roster meets project requirements before creating the .squad workspace. This prevents unintended team structures and validates the casting strategy.