new-entity-requirements

Terraform entity requirements are gathered by scanning API clients like go-elasticsearch and kbapi, analyzing Elastic API docs, and interviewing stakeholders to fill gaps. This process drafts an OpenSpec proposal defining the minimal change needed for the new entity.

The OpenSpec workflow for a new Terraform resource involves creating a change under openspec/changes, generating artifacts like proposal.md, design.md, tasks.md, and delta specs. It iteratively resolves questions via an interview to ensure decisions are captured as formal requirements.

An OpenSpec change proposal for an Elastic API data source is created by compiling API surface information from code and docs to define scope. Stakeholder interviews resolve ambiguities, producing organized artifacts under openspec/changes/<name>/.

A requirements interview for a new Terraform entity is needed when initial API client scanning and Elastic docs review leave gaps or ambiguities. The interview resolves open points, maintains traceability to source documents, and ensures decisions have clear acceptance criteria.

Yes, the requirements gathering process works with go-elasticsearch and kbapi by systematically scanning these API clients to identify the minimal OpenSpec change. It exposes unresolved questions as open points and captures decisions as formal requirements.

A limitation of using OpenSpec for Terraform entity requirements is that it produces a change proposal with delta specs, not a hand-written spec under openspec/specs/ alone. Unresolved questions remain as open points until the interview process is fully completed.