tf-domain-taxonomy

Apply an 8-category taxonomy to detect ambiguity in Terraform specifications.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/hashi-demo-lab/terraform-provider-aap --skill tf-domain-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tf-domain-taxonomy
Source: https://github.com/hashi-demo-lab/terraform-provider-aap/tree/main/.claude/skills/legacy_skills/tf-domain-taxonomy
Command: npx skills add https://github.com/hashi-demo-lab/terraform-provider-aap --skill tf-domain-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform infrastructure specifications often suffer from ambiguity across requirements, scope, and integration points. This taxonomy provides a structured approach to identify, categorize, and prioritize gaps to improve clarity and decision-making.

Core Features & Use Cases

  • 8-category ambiguity taxonomy for Terraform specs, enabling structured scans
  • Structured scan methodology to evaluate a specification step by step
  • Prioritization heuristics using Impact × Uncertainty to rank clarifications
  • Clarification question patterns to drive concrete decisions
  • Preloaded by sdd-clarify agent to accelerate AI-assisted reviews of Terraform designs

Quick Start

Run a taxonomy scan on a Terraform specification to identify ambiguity categories and prioritize clarifications.

Frequently Asked Questions about tf-domain-taxonomy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect ambiguity in Terraform specifications?

Detecting ambiguity in Terraform specifications involves applying an 8-category taxonomy across functional scope, data models, operational workflows, and non-functional attributes to systematically identify and categorize requirement gaps.

What is the best way to prioritize clarification questions for Terraform module design?

Prioritizing Terraform clarification questions requires using Impact × Uncertainty heuristics to rank gaps, driving concrete stakeholder alignment and next steps for module design decisions.

How do I structure a Terraform architecture review to find missing requirements?

Structure a Terraform architecture review by running a step-by-step taxonomy scan that evaluates the specification against predefined categories to surface missing requirements and integration point ambiguities.

Can I use this taxonomy to align stakeholders on Terraform non-functional requirements?

Yes, you can use the taxonomy to align stakeholders on Terraform non-functional requirements by generating structured clarification question patterns that translate ambiguous specifications into concrete decisions.

Do I need a pre-existing Terraform specification to run an ambiguity analysis?

Yes, you need a pre-existing Terraform specification to run an ambiguity analysis, as the taxonomy scan evaluates your current specification text step by step to identify gaps across functional and operational categories.