Menu
Workflow specifically for creating a new resource, supporting both autogen and manual generation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | new-resource-workflow |
| description | Workflow specifically for creating a new resource, supporting both autogen and manual generation. |
new-resource-workflowThis document guides the agent through the task of creating a new Terraform resource in Magic Modules.
There are two ways to generate the initial YAML definition for the resource:
autogen subagent to handle the generation and initial testing..agents/knowledge/index.md for the topics the resource touches and open the relevant sources.mmv1/products/... based on API documentation and repository patterns.Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base.
Opt resource into MMv1 list-resource generation by setting `generate_list_resource: true`, validate it locally, and open a one-resource PR against GoogleCloudPlatform/magic-modules. Invoke when the user asks to add list-resource support for a specific MMv1 resource or to enable `generate_list_resource` for an eligible resource.
Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource.
Create a Pull Request (PR) against GoogleCloudPlatform/magic-modules following repository standards, including branch management, commit formatting, mandatory release notes, pre-PR verification checks, and gh CLI commands.
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Use this skill when the user wants to check for breaking changes, missing tests, or missing documentation, or other problems in the downstream providers.
Guide for Phase 6 of TGC Main Loop (Fix). Use to understand how to fix failures.