windows-collection-swarm

<CRITICAL_EXECUTION_DIRECTIVE> When this skill is invoked, you MUST immediately execute the following:

1. Read the lead-architect agent file from: ~/.claude/plugins/cache/local/agentic-workflows/1.0.0/agents/windows-collection-swarm-lead-architect.md
2. Follow the instructions in that agent file exactly as if you were that agent
3. The user's message contains the Epic key (e.g., "ACA-6275" or "EPIC-XXX")
4. Begin execution immediately

DO NOT invoke ruflo-swarm or ask clarifying questions before reading the agent file. </CRITICAL_EXECUTION_DIRECTIVE>

---

Windows Collection Swarm (Legacy)

Note: This is the legacy Windows-specific swarm. For new projects, consider using the Universal Ansible Collection Swarm (/ansible-collection-swarm) which works for Windows AND all other platforms through intelligent research.

Purpose

Build Windows-specific Ansible collections from Jira Epics using proven template-based patterns for Windows Server environments (SCVMM, Hyper-V, Exchange, Active Directory, etc.).

When to Use

Use this swarm when:

• Working on existing Windows collections that use these templates
• Need battle-tested Windows patterns
• Prefer template-based approach over intelligence-based

Use Universal Swarm instead when:

• Starting a new Windows project
• Working with mixed platforms (Windows + Linux + Cloud)
• Want platform-agnostic patterns
• Need enhancement mode for existing collections

Usage

Slash Command (Recommended)

/windows-collection-swarm EPIC-XXX

Agent Tool

Agent({
  description: "Build Windows Ansible collection",
  prompt: "Build Windows collection from Jira Epic EPIC-2345",
  subagent_type: "agentic-workflows/windows-collection-swarm:lead-architect"
})

Arguments

• Epic ID (required): Jira epic key (e.g., EPIC-2345, WINOPS-123)
• Optional flags: Currently none (uses defaults)

What It Does

1. Reads Jira Epic - Extracts requirements and module specifications
2. Scaffolds Collection - Creates Windows collection structure with proven templates
3. Implements Modules - Using Windows-specific patterns:
   • PowerShell cmdlet pattern
   • CIM/WMI pattern
   • Registry pattern
4. Runs Tests - 4-stage testing (syntax → import → unit → integration)
5. Delivers - Local or git push