メニュー
Implements infrastructure provisioning based on approved design and tasks. Executes Terraform plans and applies changes while ensuring compliance with security and best practices.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Generates design, plan and detailed tasks based on infrastructure requirements. Reviews design against security and Terraform best practices.
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.
Automate Terraform Cloud/Enterprise operations: create workspaces, trigger runs, manage variables, and search registries for infrastructure-as-code projects.
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.
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.
| 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. |
$ARGUMENTS
Before starting the workflow, read the GitHub issue and branch details from specs/{FEATURE}/gh-issue.json using gh issue view command
in-progress label when starting work using gh issue edit <issue-number> --add-label "in-progress"🤖 **[Stage Name]** - [Started/Completed]: Brief summary🤖 **speckit.specify** - Started: Creating feature specification from requirements🤖 **speckit.specify** - Completed: Generated spec.md with 5 core requirementsAll 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.
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.
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.specify/scripts/bash/validate-env.shspeckit.implement - Generate Terraform code and test in sandbox workspace (init, plan only)terraform init/plan/apply via CLI (NOT MCP create_run)