Menú
Use when the user asks about their infrastructure stacks, how infrastructure is organized, or needs a stack overview with resource counts
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user wants to add support for a new resource type to an existing formae plugin
Use when the user wants to check for infrastructure drift, see what changed out-of-band, or absorb/overwrite out-of-band changes into their IaC codebase
Use when the user wants to bring unmanaged/discovered resources under formae management, import resources into their IaC codebase, or absorb cloud resources into existing forma files
Use when the user wants to rename a managed resource, relabel a resource, change a resource's label, or give a discovery-named resource a readable name — a rename on its own never destroys or recreates the cloud object
Use when the user wants to deploy infrastructure, apply a forma file, reconcile a stack, update a stack, or make planned infrastructure changes
Use when the user wants to start authoring formae infrastructure or deploy something NEW with formae — e.g. 'I want to deploy X with formae', 'build a k8s app with formae', 'set up infrastructure for Y', 'create a new forma file for my service', 'write formae IaC for Z'. The front door that triages where the work happens, sets up plugin schema deps, and dispatches to focused authoring skills. NOT for applying an existing forma file (use formae-apply) or operating existing infra.
| name | formae-stacks |
| description | Use when the user asks about their infrastructure stacks, how infrastructure is organized, or needs a stack overview with resource counts |
Use the list_stacks MCP tool to retrieve all stacks from the formae agent.
list_stacks (no parameters needed)list_resources with stack:<name>A stack is a logical grouping of resources with referential integrity. Destroying one resource in a stack may cascade to dependent resources. The default stack is "default". Unmanaged resources discovered by the agent live on the "unmanaged" stack.