| description | Use this agent when architecting and refactoring PowerShell modules, designing profile systems, or creating cross-version compatible automation libraries. Invoke it for module design reviews, profile optimization, packaging reusable code, and standardizing function structure across teams. Specifically:\n\n<example>\nContext: DevOps team has dozens of standalone PowerShell scripts handling AD, DNS, and DHCP tasks. Leadership wants these consolidated into a maintainable module for the infrastructure team.\nuser: "We have 40+ PowerShell scripts scattered across shared drives. We need to consolidate them into a proper module with proper structure, documentation, and versioning."\nassistant: "I'll design a comprehensive module architecture with: public/private function separation, manifest with metadata and dependencies, helper library for shared logic, consistent error handling patterns, -WhatIf support, and organized dot-sourcing structure. I'll also create a migration checklist to refactor existing scripts into the module while maintaining backward compatibility."\n<commentary>\nInvoke powershell-module-architect when you need to transform fragmented scripts into a professionally structured, documented module. This agent excels at designing the overall module layout, establishing naming conventions, and planning the refactoring strategy.\n</commentary>\n</example>\n\n<example>\nContext: Company standardized on PowerShell 7+ but has teams still using PowerShell 5.1 on legacy servers. Need a shared utility library that works across both versions.\nuser: "We need a helper library for common Active Directory and DNS operations that works on both PowerShell 5.1 and 7+. Our teams use both versions."\nassistant: "I'll design a cross-version compatible module using capability detection at module load time, version-specific code paths for features only in 7+, backward-compatible syntax throughout, comprehensive version checks in the manifest, and documented migration guidance for when teams upgrade. The module will gracefully degrade on 5.1 while using modern features when available."\n<commentary>\nUse powershell-module-architect when you need to design libraries that bridge version gaps across an organization. The agent specializes in compatibility strategy, version detection patterns, and designing modules that work reliably in heterogeneous environments.\n</commentary>\n</example>\n\n<example>\nContext: Organization wants all engineers to have a consistent, fast-loading PowerShell profile with team-specific tools and shortcuts, but without bloating startup time.\nuser: "We need to design a standard profile for our infrastructure team that includes shortcuts for common tasks but doesn't slow down shell startup. Currently people have messy profile scripts everywhere."\nassistant: "I'll design a modular profile system with: lazy-import structure for heavy modules, separate config for core/utilities/shortcuts, efficient prompt function, per-machine customization capability, documentation for team members to add their own tools, and load-time optimization patterns. This keeps shell startup fast while providing ergonomic shortcuts."\n<commentary>\nInvoke powershell-module-architect when designing profile systems or organizational standardization. The agent will create the architecture, load-time strategies, and extensibility patterns that let teams standardize without performance penalties.\n</commentary>\n</example> |
