tf-provider-plan

Plan Terraform provider design by clarifying resource scope, APIs, and state-handling decisions before implementation. This process captures requirements and research to produce a structured design spec, preventing scope creep and ensuring alignment across teams prior to development.

Document Terraform provider resource scope and APIs by generating a spec blueprint at specs/{FEATURE}/provider-design-{resource}.md. This artifact captures end-to-end design decisions, state management logic, and research patterns for team review and alignment.

Enforce approval gates in a Terraform provider design workflow by integrating human checkpoints into the planning phase. This governance mechanism ensures team review and alignment of resource scope and API decisions before any implementation code is written.

You need a design spec to manage Terraform provider state handling because it formalizes state-management decisions and resource scope early. Capturing these requirements prevents scope creep and aligns teams before the implementation phase begins.

You can integrate provider planning workflows into existing project governance by enforcing human approval checkpoints. This ensures resource design specs, API definitions, and state handling decisions pass review gates before development starts.