| id | pulumi-specialist |
| name | pulumi-specialist |
| type | skill |
| version | 1.0.0 |
| domain | ["infra"] |
| platform | ["pulumi"] |
| task | ["debugging","review"] |
| maturity | validated |
| description | Deep-dive Pulumi stack review, component design, Automation API audit, and secrets management. Use for structured investigations of Pulumi stack drift, ComponentResource coupling, ESC configuration, and Automation API workflows. Triggers on: "Pulumi audit", "stack review", "Automation API review", "ComponentResource design", "ESC audit", "Pulumi secrets", "Pulumi testing".
|
| argument-hint | <stack name, project path, or problem description> |
| tools | Read, Grep, Glob, Bash |
| effort | max |
| model | opus |
Pulumi Specialist
Structured investigation for Pulumi infrastructure codebases. Five phases:
gather context, diagnose, design, recommend, verify.
Arguments
$0 — stack name, project path, or problem description. Required.
Phase 1: Context Gathering
- Identify the Pulumi project:
cat Pulumi.yaml
pulumi stack ls
- Inspect the active stack config:
pulumi config --show-secrets
pulumi stack output
- Glob for Pulumi source files:
find . -name "*.ts" -o -name "*.py" -o -name "*.go" | grep -v node_modules | sort
- Check for Automation API usage:
grep -r "LocalWorkspace\|RemoteWorkspace\|createStack\|selectStack" . \
--include="*.ts" --include="*.py" --include="*.go" -l
Phase 2: Diagnosis
Stack health:
pulumi preview --diff
pulumi stack --show-ids
Resource graph:
pulumi stack graph --dependency-graph /tmp/graph.dot
dot -Tsvg /tmp/graph.dot -o /tmp/graph.svg
Secret exposure check:
pulumi config --show-secrets | grep -i "key\|secret\|password\|token"
pulumi stack output --show-secrets
Test coverage:
find . -name "*.test.ts" -o -name "*_test.go" -o -name "test_*.py" | sort
Phase 3: Design / Root-Cause Analysis
Map symptoms to causes:
| Symptom | Common Causes | Check |
|---|
