init-mode

Coordinate phased team initialization workflows with user confirmation gating.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill init-mode-waynewalterberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill init-mode-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a phased team initialization workflow from initial proposal to actual creation, ensuring no files or artifacts are generated without explicit user confirmation. It enforces a gating step and provides a clear structure for capturing rosters, casting decisions, and governance context.

Core Features & Use Cases

  • Phase 1: Propose a team roster and cast, without committing any changes.
  • Confirmation gating: prompt the user to confirm the roster before proceeding (prevents accidental changes).
  • Phase 2: Create the .squad workspace structure and seed initial context (policy, history, agents).
  • Casting foundation: assign roles (Lead, Frontend, Backend, Scribe, Monitor) and prepare cross-agent artifacts for onboarding.
  • Governance artifacts: decisions, ritual notes, and logs prepared for future collaboration.

Quick Start

Initiate Phase 1 by proposing a team roster and solicit explicit user confirmation before creating any files.

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 team roster without creating files prematurely?

Team initialization can propose a roster and cast without committing changes by using a gating step that requires explicit user confirmation before generating any files or artifacts.

What is the phased workflow for setting up a new project roster?

The phased workflow splits team setup into Phase 1 proposals for rosters and roles, followed by Phase 2 creation of the squad workspace, policies, and history seeds upon user confirmation.

How do I assign roles like Lead and Frontend during team initialization?

Role assignment uses a casting foundation to designate roles such as Lead, Frontend, Backend, Scribe, and Monitor, preparing cross-agent artifacts for onboarding during the initialization process.

Can I review the proposed team structure before any workspace files are generated?

Yes, confirmation gating prompts you to review and explicitly confirm the proposed team roster before the system proceeds to create the workspace structure and seed initial context.

What governance artifacts are created during the squad setup process?

The squad setup seeds initial governance artifacts including decisions, ritual notes, and logs, alongside policy and history seeds prepared for future team collaboration.