init-mode

Initialize team roster and squad state after user confirmation.

49|6|Updated Aug 24, 2021

Search Tags:#automation #workflow #orchestration #ai-agent #casting #team-initiation #roster-confirmation

Ready to run

npx skills add https://github.com/webmaxru/bpm-counter --skill init-mode-webmaxru

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Team initialization requires careful coordination and explicit approvals to avoid misconfiguration and scope creep. This Skill automates the initial roster proposal, collects confirmation, and sets up the squad state to enable Phase 2 creation.

Core Features & Use Cases

Proposes a cross-functional roster for Phase 1 and waits for user confirmation before any files are created.
Initializes the .squad state, including casting state, templates, and agents, to support subsequent Phase 2 execution.
Enforces explicit confirmation via the ask_user tool to guard against accidental changes and ensure traceability.

Quick Start

Prompt the user to confirm the proposed roster before any files are created.

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 setup with explicit roster confirmation before execution?▼

Automating team setup requires proposing a cross-functional roster and waiting for user confirmation before creating files. This workflow initializes the .squad state, including casting state and templates, to enable subsequent Phase 2 execution safely.

Why do I need explicit user approval for workflow orchestration during team initiation?▼

Explicit user approval for workflow orchestration prevents accidental changes and scope creep. By enforcing confirmation via the ask_user tool prior to Phase 2 execution, it ensures traceability and guards against misconfiguration during initial team setup.

What is casting state initialization and when do I need it for AI agent orchestration?▼

Casting state initialization sets up the .squad state with agents and templates to support Phase 2 creation. You need it when coordinating cross-functional team setup to ensure required roster roles and states are provisioned before workflow actions begin.

Can I initialize cross-functional team rosters without creating files until confirmed?▼

Yes, you can propose a cross-functional roster for Phase 1 and wait for explicit user confirmation before any files are created. This approach ensures the proposed squad state and templates are safely provisioned without accidental modifications.

What's the best way to coordinate Phase 1 team setup and avoid scope creep?▼

The best way to coordinate Phase 1 team setup is to automate roster proposals and enforce explicit confirmation. Initializing the squad state only after approval prevents scope creep and ensures template provisioning happens securely.

Does team initiation require manual approval before provisioning templates for Phase 2?▼

Team initiation requires manual approval before provisioning templates for Phase 2. The system enforces explicit user confirmation via the ask_user tool to guard against accidental changes and ensure traceability before executing any subsequent actions.