entity-requirements

To generate OpenSpec requirements from existing Terraform code, provide the entity path and the skill analyzes the resource or data source implementation to produce a standards-compliant spec.md under openspec/specs.

Yes, you can document Terraform resources built with both the plugin-framework and SDK. The skill analyzes both entity types to capture attributes, CRUD behavior, and error handling into verifiable requirements.

The best way to auto-document Terraform resource schemas and behavior is to analyze the code path directly, mapping attributes, CRUD operations, and error handling to a traceable OpenSpec specification.

No, generating OpenSpec documentation does not require manually writing the schema section. The skill derives the schema and requirements directly from the Terraform entity implementation code path.

Using code analysis to create Terraform resource specifications ensures traceability from implementation to documentation. It maps attributes and CRUD behavior directly to verifiable requirements, reducing manual documentation drift.

A limitation when auto-generating OpenSpec requirements from Terraform implementations is that the output focuses on purpose, schema, and requirements sections derived directly from the code path, requiring existing implementation logic to be present.