init-mode

Propose a project roster and create the team structure after user confirmation.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill init-mode-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-mode
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/init-mode
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill init-mode-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables a coordinated kickoff by proposing a Phase 1 roster and safely creating the Phase 2 team structure after explicit user confirmation.

Core Features & Use Cases

  • Propose the team roster using an interactive ask_user menu.
  • Require user confirmation before moving to Phase 2 and creating the team structure.
  • Initialize and seed the .squad directory with planning artifacts and memories after approval.
  • Maintain an append-only log of decisions and history to support audit and collaboration.

Quick Start

Propose a roster and confirm to trigger Phase 2 creation.

Frequently Asked Questions about init-mode

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

FAQPage Schema
How do I set up a project squad with a phased team initiation process?

Project squad setup uses an interactive menu to propose a Phase 1 roster, then requires explicit user confirmation to trigger Phase 2 team structure creation and initialize the .squad directory.

What is the best way to coordinate kickoff and governance for workflow orchestration tasks?

Kickoff coordination is handled by proposing an initial project roster and safely creating a staged team construction process gated by explicit user confirmation before initializing state artifacts.

Can I require user confirmation before moving to Phase 2 of team construction?

Yes, the workflow requires explicit user confirmation before moving to Phase 2, ensuring safe initialization of the .squad state and preventing premature team structure creation.

How does the .squad directory initialization work for formalized team rosters?

The .squad directory initialization seeds planning artifacts and memories after approval, creating an append-only log of decisions and history to support audit and collaboration for the project squad.

Does this workflow orchestration approach support audit and collaboration tracking?

Audit and collaboration tracking is supported through an append-only log of decisions and history maintained within the .squad directory after Phase 2 team structure creation is approved.

When do I need formalized team rosters and staged team construction for project startups?

Formalized team rosters and staged team construction are needed for project startups requiring coordinated kickoff and governance, where Phase 1 proposal and Phase 2 creation must be gated by user confirmation.