init-mode

Propose a team roster, confirm with the user, then create the team structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to initialize a project team in two phases: proposal and creation, ensuring explicit user confirmation before any files or structures are created.

Core Features & Use Cases

  • Phase 1: Propose the team using a casting process to determine roles and roster without altering the project yet.
  • Use the ask_user tool to confirm or adjust the roster, ensuring explicit user consent before proceeding.
  • Phase 2: Create the team structure, seed agent context, and initialize persistence state after confirmation.
  • Suitable for projects requiring formal team setup, governance, and traceable decision logs.

Quick Start

Prompt the coordinator to propose a team, then confirm the roster before proceeding 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 team initialization for a squad while requiring explicit approval before committing roles?

Automated team initialization orchestrates squad setup in two phases, proposing roles and roster first, then requiring explicit user confirmation before creating any team structure or files.

What is phased team setup and how does it ensure safe project orchestration?

Phased team setup separates proposal and creation stages to ensure safe project orchestration. It proposes team casting first, then creates structures and initializes persistence state only after user consent.

How do I prompt users to confirm a roster before seeding agent context and initializing state?

You prompt users to confirm a roster by using an ask_user mechanism during the proposal phase, ensuring explicit consent before proceeding to seed agent context and initialize state.

Does team initiation workflow support append-only logging for governance and traceable decisions?

Yes, team initiation workflows support safe, append-only logging of decisions, satisfying project requirements for formal governance and maintaining traceable decision records during setup.

Can I adjust the proposed roles during the casting process before the team structure is created?

Yes, you can adjust proposed roles during the casting process. The proposal phase allows modifications to the roster based on user feedback before any project files are created.

When should I use an automated workflow for project team setup instead of manual configuration?

Use automated workflow for project team setup when you need formal governance, explicit user approval phases, coordinated casting, and traceable decision logs for initializing complex squad structures.