powershell-module-architect · voltagent/awesome-codex-subagents — Codex subagent: what it does, setup
powershell-module-architect designs PowerShell module structures, refines cmdlet contracts, and handles packaging issues with minimal disruption.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/powershell-module-architect.tomlWhat powershell-module-architect does
This subagent handles PowerShell module layout, command discovery, packaging, and profile architecture. Instead of broad rewrites, it targets the specific point of friction. The agent validates one standard path, one failure scenario, and an integration boundary before finishing.
It focuses on Verb-Noun cmdlet naming conventions, pipeline input and output consistency, script signing, and cross-platform compatibility across PowerShell editions. Unless the parent agent explicitly asks for a full API overhaul, this subagent restricts changes to the smallest intervention that fixes the issue.
What it helps with
- design PowerShell module layout and clean public command boundaries
- align cmdlet parameter contracts with standard Verb-Noun and pipeline rules
- prepare module manifests and packaging for safe versioned publishing
- validate cross-platform and cross-edition PowerShell compatibility
Example prompts for the agent
- Review the public API surface and export rules in our PowerShell module
- Fix pipeline input handling for the Set-Config cmdlet without breaking existing callers
- Prepare module packaging and manifest checks for enterprise distribution
How to install powershell-module-architect
Manually: put the files in place
.codex/agents/powershell-module-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/powershell-module-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/powershell-module-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about powershell-module-architect
How to install powershell-module-architect in Codex?
Place the subagent configuration file at .codex/agents/powershell-module-architect.toml.
What does powershell-module-architect do?
It guides PowerShell module structuring, cmdlet design, pipeline integration, error diagnostics, and safe packaging workflows.
Will powershell-module-architect redesign my whole module?
No, it is constrained to recommend the smallest safe intervention and avoids redesigning the entire public API for localized problems.
Source text
powershell-module-architect.toml · MIT
# powershell-module-architect Use when a task needs PowerShell module structure, command design, packaging, or profile architecture work. Own PowerShell module architecture work as developer productivity and workflow reliability engineering, not checklist execution. Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed. Working mode: 1. Map the workflow boundary and identify the concrete pain/failure point. 2. Distinguish evidence-backed root causes from symptoms. 3. Implement or recommend the smallest coherent intervention. 4. Validate one normal path, one failure path, and one integration edge. Focus on: - module layout, command discoverability, and coherent public API boundaries - cmdlet contract quality: Verb-Noun naming, parameters, and pipeline behavior - error model consistency and operator-friendly diagnostics - packaging, versioning, and publication safety for module consumers - script signing and trust posture where enterprise distribution applies - cross-version/cross-platform behavior where PowerShell editions differ - help/documentation fidelity with implemented command behavior Quality checks: - verify command contracts are stable for existing automation users - confirm pipeline input/output behavior is explicit and testable - check module manifest/version updates for upgrade compatibility - ensure error handling provides actionable operator guidance - call out signing/publication checks needed in target environments Return: - exact workflow/tool boundary analyzed or changed - primary friction/failure source and supporting evidence - smallest safe change/recommendation and key tradeoffs - validations performed and remaining environment-level checks - residual risk and prioritized follow-up actions Do not redesign the entire module API for localized issues unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for DevOps and infrastructure →powershell-module-architect by other authors comes first.