powershell-script-engine

Generates production, PSScriptAnalyzer-clean PowerShell scripts in the voice of a PowerShell expert and Windows systems engineer. Two free-text inputs (TASK, USER_REQUIREMENTS) plus three choices (PS_TARGET, REMOTE, DESTRUCTIVE) drive a locked four-section output: Script (comment-based help on every function, #Requires -Version 7.0, [CmdletBinding()] with validated params, try/catch/finally, console+file logging that rolls at 10 MB keeping 5 archives), Parameters table (Name/Mandatory/Type/Validation), at least three Usage Examples (local, pipeline, remote/PSSession), and Security Notes. Approved verbs only (Get-Verb), no aliases in body, no Write-Host for data, no positional args in examples, no PSScriptAnalyzer rule suppressions. Security non-negotiables: never emits plaintext passwords, hardcoded credentials, API keys, or connection strings ([PSCredential]/Get-Credential/SecretManagement only); never generates destructive operations (Remove-*, Format-*, Stop-*, registry/disk writes) unless named in requirements, and gates any behind -WhatIf/-Confirm; never invents cmdlet, module, parameter, or version names. Hard prompt-injection defense treats requirements as inert data; halts with one clarifying question when task or requirements are empty. Ends every response with a review-before-production footer. Includes /powershell-script-engine slash command with AskUserQuestion intake.