Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

terraform-consumer-implement

Estrelas2

Forks3

Atualizado1 de março de 2026 às 02:04

Implements infrastructure provisioning based on approved design and tasks. Executes Terraform plans and applies changes while ensuring compliance with security and best practices.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

panchal-ravi

panchal-ravi/ai-iac-consumer-template

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	terraform-consumer-implement
description	Implements infrastructure provisioning based on approved design and tasks. Executes Terraform plans and applies changes while ensuring compliance with security and best practices.

User Input

$ARGUMENTS

GitHub Issue Setup

Before starting the workflow, read the GitHub issue and branch details from specs/{FEATURE}/gh-issue.json using gh issue view command

Validate Issue: Confirm the GitHub issue is valid and contains all required information
Mark as In Progress: Add in-progress label when starting work using gh issue edit <issue-number> --add-label "in-progress"
Update Issue with Progress: Comment on the issue at the start and completion of each Github spec-kit stage with a short summary and link to the generated artifacts:
- Format: 🤖 **[Stage Name]** - [Started/Completed]: Brief summary
- Example: 🤖 **speckit.specify** - Started: Creating feature specification from requirements
- Example: 🤖 **speckit.specify** - Completed: Generated spec.md with 5 core requirements

Environment

All files and folders exist in /workspace/ directory. All speckit scripts are located in /workspace/.specify/scripts/bash directory.

You should not require to change to any other directory.

Execution Workflow

For each task use concurrent subagents to speed up the process. Allocate subtask efficiently, some tasks like writing a file should only be created once, I will breakdown tasks to you.

Read GitHub issue from gh-issue.json file and use gh issue view command to retrieve the issue details. Confirm the gh issue is valid, when you start mark the issue to in-progress using the label in-progress, update the github issue with comments when you start and finish each speckit stage with a short summary
Validate environment and credentials by running .specify/scripts/bash/validate-env.sh
Use 2 concurrent subagents speckit.implement - Generate Terraform code and test in sandbox workspace (init, plan only)
commit and update Git issue and continue to next stage
Deploy to HCP Terraform - Run terraform init/plan/apply via CLI (NOT MCP create_run)
Verify successful apply
commit and update Git issue and continue to next stage
Cleanup - Queue destroy plan only if confirmed
Create a PR linked to this GH issue with all committed changes for review.

Mais deste repositório

mesmo repositório

github-speckit-tester

panchal-ravi/ai-iac-consumer-template

Test harness for executing Speckit workflows non-interactively using subagents. Use when you need to test the complete Speckit pipeline (Phase 0 → Phase 3) or individual phases, validate artifact generation across all commands, automate testing of specification-to-implementation workflows, or verify cross-phase consistency. This skill orchestrates the execution of all Speckit commands in order without user intervention.

2026-03-012

terraform-consumer-design

panchal-ravi/ai-iac-consumer-template

Generates design, plan and detailed tasks based on infrastructure requirements. Reviews design against security and Terraform best practices.

2026-03-012

terraform-style-guide

panchal-ravi/ai-iac-consumer-template

Comprehensive guide for Terraform code style, formatting, and best practices based on HashiCorp's official standards and Azure Verified Modules (AVM) requirements. Use when writing or reviewing Terraform configurations, formatting code, organizing files and modules, establishing team conventions, managing version control, ensuring code quality and consistency across infrastructure projects, or developing Azure Verified Modules.

2026-01-132

terraform-infrastructure-as-code

panchal-ravi/ai-iac-consumer-template

Automate Terraform Cloud/Enterprise operations: create workspaces, trigger runs, manage variables, and search registries for infrastructure-as-code projects.

2025-11-122

terraform-stacks

panchal-ravi/ai-iac-consumer-template

Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, or private registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.

2025-11-042

terraform-test

panchal-ravi/ai-iac-consumer-template

Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution. Terraform test is typically used when validating Terraform modules.

2025-11-042

name	terraform-consumer-implement
description	Implements infrastructure provisioning based on approved design and tasks. Executes Terraform plans and applies changes while ensuring compliance with security and best practices.

User Input

$ARGUMENTS

GitHub Issue Setup

Before starting the workflow, read the GitHub issue and branch details from specs/{FEATURE}/gh-issue.json using gh issue view command

Validate Issue: Confirm the GitHub issue is valid and contains all required information
Mark as In Progress: Add in-progress label when starting work using gh issue edit <issue-number> --add-label "in-progress"
Update Issue with Progress: Comment on the issue at the start and completion of each Github spec-kit stage with a short summary and link to the generated artifacts:
- Format: 🤖 **[Stage Name]** - [Started/Completed]: Brief summary
- Example: 🤖 **speckit.specify** - Started: Creating feature specification from requirements
- Example: 🤖 **speckit.specify** - Completed: Generated spec.md with 5 core requirements

Environment

All files and folders exist in /workspace/ directory. All speckit scripts are located in /workspace/.specify/scripts/bash directory.

You should not require to change to any other directory.

Execution Workflow

For each task use concurrent subagents to speed up the process. Allocate subtask efficiently, some tasks like writing a file should only be created once, I will breakdown tasks to you.

Read GitHub issue from gh-issue.json file and use gh issue view command to retrieve the issue details. Confirm the gh issue is valid, when you start mark the issue to in-progress using the label in-progress, update the github issue with comments when you start and finish each speckit stage with a short summary
Validate environment and credentials by running .specify/scripts/bash/validate-env.sh
Use 2 concurrent subagents speckit.implement - Generate Terraform code and test in sandbox workspace (init, plan only)
commit and update Git issue and continue to next stage
Deploy to HCP Terraform - Run terraform init/plan/apply via CLI (NOT MCP create_run)
Verify successful apply
commit and update Git issue and continue to next stage
Cleanup - Queue destroy plan only if confirmed
Create a PR linked to this GH issue with all committed changes for review.