tf-module-implement

To generate a Terraform module from a design document, you need an existing design.md file located at specs/{FEATURE}/design.md. The automation workflow parses this design specification to scaffold consistent module code aligned with your feature expectations.

Test-driven development for Terraform modules involves writing tests up-front before implementing any module code. This approach validates the module against design expectations early, ensuring changes are thoroughly tested, linted, and validated before pull request creation.

You can automate Terraform module validation and PR preparation by running the module-assembly workflow with a specified feature name. This process executes automated validations, runs tests, generates code, and prepares the pull request for delivery.

Yes, a design.md file is strictly required at the specs/{FEATURE}/design.md path to scaffold Terraform modules automatically. The workflow parses this existing design specification to drive test generation, code implementation, and validation.

Yes, the Terraform TDD workflow supports automated linting and testing through validation checkpoints. It scaffolds modules consistently and applies automated agents to run validations, ensuring the generated code meets quality standards before integration.

The limitation of automating Terraform module generation is its strict dependency on an existing design.md file at specs/{FEATURE}/design.md. Without this specific prerequisite file properly structured, the automated scaffolding, testing, and PR workflow cannot execute.