[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TJ91WM8FMHTEGNW4JWRKZ":3,"skill-same:01M72TJ91WM8FMHTEGNW4JWRKZ":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72TJ91WM8FMHTEGNW4JWRKZ","ywc-iac-author",null,"(ywc) Use when authoring Terraform from a design for AWS, GCP, Azure, or Kubernetes\u002FHelm, with validate\u002Fplan verification and a blast-radius summary. Triggers: \"IaC 작성\", \"terraform 작성\", \"write terraform\", \"IaC を書いて\", \"ywc-iac-author\". Do not use for application\u002Fbusiness logic, topology design first (use ywc-infra-design), IaC review (use ywc-infra-review), cost\u002Fright-sizing remediation (use ywc-infra-optimize), or worktree Docker port collisions (use ywc-docker-isolate).","yongwoon\u002Fywc-agent-toolkit","yongwoon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9317029?v=4","01M72SZSF6VKANKG5QTMV4V95S","01M72SZSG8HHC3W2CV5P7EJ5AH",8,"MIT","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ywc-iac-author\ndescription: >-\n  (ywc) Use when authoring Terraform from a design for AWS, GCP, Azure, or\n  Kubernetes\u002FHelm, with validate\u002Fplan verification and a blast-radius\n  summary. Triggers: \"IaC 작성\", \"terraform 작성\", \"write terraform\", \"IaC\n  を書いて\", \"ywc-iac-author\". Do not use for application\u002Fbusiness logic,\n  topology design first (use ywc-infra-design), IaC review (use\n  ywc-infra-review), cost\u002Fright-sizing remediation (use\n  ywc-infra-optimize), or worktree Docker port collisions (use\n  ywc-docker-isolate).\n---\n\n# ywc-iac-author\n\n**Announce at start:** \"I'm using the ywc-iac-author skill to author Terraform from a design, verify it with validate\u002Fplan, and summarize the blast radius.\"\n\nThis skill is the Infrastructure-as-Code counterpart to `ywc-code-gen`: it turns an infrastructure design into working Terraform, dispatches per-module authoring to a Codex worker carrying the `ywc-cloud-engineer` persona (single-responsibility infra worker — the infra counterpart to `ywc-backend-coder`), verifies with `terraform validate` \u002F `terraform plan`, and reports a blast-radius summary before anything is applied. **Terraform is the single fixed IaC tool for this toolkit** — Kubernetes and Helm resources are expressed through the Terraform `kubernetes` \u002F `helm` providers, never raw manifests, a standalone Helm chart, or a second IaC tool (Pulumi \u002F CDK \u002F CloudFormation \u002F Bicep).\nThis skill is the Infrastructure-as-Code counterpart to `ywc-code-gen`: it turns an infrastructure design into working Terraform inside the current Codex session, uses the read-only `ywc-cloud-engineer` persona for feasibility and blast-radius advisory where helpful, verifies with `terraform validate` \u002F `terraform plan`, and reports a blast-radius summary before anything is applied. **Terraform is the single fixed IaC tool for this toolkit** — Kubernetes and Helm resources are expressed through the Terraform `kubernetes` \u002F `helm` providers, never raw manifests, a standalone Helm chart, or a second IaC tool (Pulumi \u002F CDK \u002F CloudFormation \u002F Bicep).\n\n## Rationalization Defense\n\nWhen tempted to bypass a rule, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"No `infra-design.md` exists — I'll just infer the topology and start writing Terraform\" | Inferring topology duplicates `ywc-infra-design`'s decision and compounds the error downstream. Either ask the user to run `$ywc-infra-design` first, or explicitly clarify inline intent (service list, provider, network boundary) and record it before authoring — never guess silently. |\n| \"`terraform plan` looks safe, I'll run `apply` to confirm it actually works\" | `apply` mutates live infrastructure and is irreversible for destroy operations. This skill and its worker stop at `plan`; `apply` requires explicit human approval outside this skill's scope. |\n| \"Kubernetes work is easier as a raw manifest or a Helm chart\" | Terraform is fixed as the single IaC tool for this toolkit. K8s\u002FHelm resources go through the Terraform `kubernetes` \u002F `helm` providers so the same validate\u002Fplan\u002Fstate discipline applies uniformly — raw manifests and standalone Helm bypass that discipline. |\n| \"I'll hardcode the DB password as a default so `plan` runs cleanly\" | Hardcoded secrets leak into `.tf` files, version control, and Terraform state (which itself must never be committed). Route sensitive values through variables, `TF_VAR_*`, or a secret manager reference. |\n| \"Terraform state is only local for now, I'll commit it so the next run skips `init`\" | `*.tfstate` and `*.tfstate.backup` can contain plaintext secrets and resource IDs; committing them is a leak, not a convenience. Use a remote backend with locking (S3+DynamoDB, GCS, azurerm, Terraform Cloud) and gitignore state files. |\n| \"The plan output is long, I'll just say 'a few resources change'\" | The blast-radius summary must report the exact add\u002Fchange\u002Fdestroy counts and name every destroy against a stateful resource (DB, bucket, volume) explicitly — vague summaries hide data-loss risk from the reviewer. |\n| \"This is a tiny IaC change, I'll skip recommending `ywc-infra-review`\" | Even small Terraform diffs can widen a security group or loosen an IAM policy. Recommending `$ywc-infra-review` after authoring is not optional ceremony — it is the pre-apply safety net this skill hands off to. |\n\n**Violating the letter of these rules is violating the spirit.** An IaC authoring pass that skips validate\u002Fplan discipline or applies without review turns a code review problem into a production incident.\n\n## Arguments\n\n| Parameter | Format | Example | Description |\n|-----------|--------|---------|-------------|\n| `--design-doc` | `--design-doc \u003Cpath>` | `--design-doc infra-design.md` | Path to the `ywc-infra-design` output to load as the authoring input. Omit to fall back to inline intent clarification (Step 1). |\n| `--scope` | `--scope \u003Cmodule-path>` | `--scope infra\u002Fmodules\u002Fnetwork` | Restrict authoring to a single Terraform module. Default: every module implied by the design input. |\n| `--skip-review-recommendation` | flag | `--skip-review-recommendation` | Skip the closing `ywc-infra-review` recommendation. Only valid when the upstream caller already schedules review itself. |\n\n## Workflow\n\n### Step 1: Load the design input, or clarify inline intent\n\nIf `--design-doc` is provided or an `infra-design.md` (the `ywc-infra-design` output contract) exists in the working context, load it as the authoring source of truth: service list, network topology, IAM boundaries, data stores, and the reliability\u002Fcost\u002Fsecurity trade-off notes it recorded.\n\nIf no design input exists, do not infer the topology. Clarify inline with the user: target provider (AWS\u002FGCP\u002FAzure\u002FK8s), the services\u002Fresources involved, and any network or IAM constraints — then record that intent before moving to Step 2. For anything beyond a small, well-understood change, recommend the user run `$ywc-infra-design` first.\n\n### Step 2: Load the fixed IaC tool reference\n\nRead `..\u002Freferences\u002Finfra\u002Fiac\u002Fterraform.md` — the canonical `fmt → init → validate → plan → (human approval) → apply` workflow, blast-radius reporting shape, and state-management guards. This is the only IaC-tool reference this skill loads; Terraform is fixed and no other IaC tool reference exists in this toolkit.\n\nLoad the provider-specific reference matching the design's target provider — only the one file needed, per Progressive Disclosure:\n\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Faws.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fgcp.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fazure.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fk8s.md` — Kubernetes\u002FHelm via the Terraform `kubernetes`\u002F`helm` providers\n\n### Step 3: Author per Terraform module with optional advisory consult\n\nFor each Terraform module implied by the design (network, compute, data store, IAM, etc.), or a single narrowed pass when `--scope` targets one module, author the `.tf` files in the current Codex session. When provider-specific feasibility, reliability, or blast-radius judgment is unclear, consult the read-only `ywc-cloud-engineer` persona with the relevant slice of the design input and the matching provider reference from Step 2. That consult is advisory only: it does not author files, run `terraform apply`, or replace the main session's ownership of the Terraform edits.\n\n### Step 4: Verify — `terraform validate` \u002F `terraform plan`\n\nConfirm each authored module returned a clean `terraform validate` and a completed `terraform plan` (per the terraform.md verification workflow). If an advisory consult returns `BLOCKED` or `NEEDS_CONTEXT` (missing design input, unresolved provider constraint, blast-radius ambiguity), surface it rather than papering over it with a guess.\n\n### Step 5: Blast-radius summary\n\nAggregate every module's `plan` headline into one summary: total resources to add \u002F change \u002F destroy, with every destructive change against a stateful resource (database, bucket, volume, persistent disk) called out explicitly. See Output Format below for the exact shape.\n\n### Step 6: State handling and secret externalization guards\n\nBefore closing out, confirm:\n\n- No `*.tfstate` \u002F `*.tfstate.backup` \u002F `.terraform\u002F` was staged or committed.\n- No `.tfvars` file containing a literal secret was staged or committed.\n- Every credential, password, or API key in the authored `.tf` files flows through a variable, `TF_VAR_*`, or a secret-manager data source — never a hardcoded default.\n- A remote backend with locking is configured (or already exists) for any module holding state that matters beyond a single local run.\n\n### Step 7: Recommend `ywc-infra-review`\n\nUnless `--skip-review-recommendation` was passed, close the authoring pass by recommending the user run `$ywc-infra-review` before `apply` — especially when the blast radius includes a security group, IAM policy, or public-exposure change.\n\n## Output Format\n\n```text\nIaC Authoring Report\n─────────────────────────────────────────────────\nDesign input:    infra-design.md  (or \"inline intent\" if none was provided)\nTool:            Terraform (single fixed tool)\nModules authored:\n  - infra\u002Fmodules\u002Fnetwork      (authoring in current session, advisory consult optional)  validate: PASS  plan: PASS\n  - infra\u002Fmodules\u002Fdata         (authoring in current session, advisory consult optional)  validate: PASS  plan: PASS\n\nBlast radius (aggregate):\n  Plan: 9 to add, 3 to change, 1 to destroy.\n  ⚠ destroy: aws_db_instance.legacy   (stateful — confirm backup\u002Fsnapshot before apply)\n\nState handling:\n  - No *.tfstate staged or committed\n  - Remote backend: S3 + DynamoDB (configured)\n\nSecrets:\n  - 0 hardcoded credentials found; DB password routed through TF_VAR_db_password\n─────────────────────────────────────────────────\nRecommended next step: $ywc-infra-review (before apply)\n```\n\n## Validation Checklist\n\nBefore declaring the authoring pass complete, verify:\n\n- [ ] The design input was loaded, or inline intent was explicitly clarified and recorded (never silently inferred)\n- [ ] Every dispatched module returned `terraform validate` PASS\n- [ ] Every dispatched module returned a completed `terraform plan` (no live `apply` executed)\n- [ ] The blast-radius summary names every destroy against a stateful resource\n- [ ] No `.tfstate` file and no literal secret in a `.tfvars` file was staged or committed\n- [ ] Every secret in authored `.tf` files flows through a variable or secret-manager reference\n- [ ] `$ywc-infra-review` was recommended, unless `--skip-review-recommendation` was passed by an upstream caller\n\n## Common Mistakes\n\n- **Re-deriving the topology instead of loading the design input.** When `infra-design.md` exists, use it verbatim — re-deriving from scratch risks drifting from the reviewed trade-offs (network CIDR choices, IAM boundaries) that design phase already settled.\n- **Treating the advisory consult as the authoring worker.** The `ywc-cloud-engineer` persona is read-only; it can clarify feasibility or blast radius, but the current Codex session owns the Terraform edits.\n- **Treating a `NEEDS_CONTEXT` return from the advisory consult as a prompt to guess and continue.** The consult returns `NEEDS_CONTEXT` specifically when the design decision it needs is missing — surface it to the user rather than filling the gap with an assumption.\n- **Skipping Step 6's state\u002Fsecret guard because `plan` already succeeded.** `terraform plan` succeeding says nothing about whether a secret is hardcoded or whether state got staged — that check is separate and mandatory every pass.\n\n## Integration\n\n- **Upstream**: `ywc-infra-design` (produces the `infra-design.md` input contract); direct user invocation with inline intent when no design phase is warranted.\n- **Downstream**: `ywc-infra-review` (recommended after every authoring pass, mandatory before `apply` when the blast radius touches security\u002FIAM\u002Fpublic exposure).\n- **Pairs with**: `ywc-cloud-engineer` persona (the read-only specialist that advises on feasibility, reliability, and blast radius while this skill authors the Terraform).\n- **Must not be paired with**: authoring a second IaC tool in the same change (Pulumi\u002FCDK\u002FCloudFormation\u002FBicep\u002Fstandalone Helm) — Terraform is fixed.\n\n## References\n\n| Reference | Use when |\n|---|---|\n| `..\u002Freferences\u002Finfra\u002Fiac\u002Fterraform.md` | Every authoring pass — the fixed tool's verification workflow, blast-radius reporting shape, and state guards |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Faws.md` | Design's target provider is AWS |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fgcp.md` | Design's target provider is GCP |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fazure.md` | Design's target provider is Azure |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fk8s.md` | Design's target includes Kubernetes\u002FHelm (via Terraform providers) |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Fsecurity.md` | Spot-checking for an obvious misconfiguration (public bucket, open security group) while authoring, ahead of the full `ywc-infra-review` pass |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Fcost.md` | Flagging an obviously oversized resource while authoring, ahead of `ywc-infra-optimize` |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Freliability.md` | Confirming a new module has basic redundancy\u002Fbackup coverage before handing off to review |\n","# ywc-iac-author\n\n**Announce at start:** \"I'm using the ywc-iac-author skill to author Terraform from a design, verify it with validate\u002Fplan, and summarize the blast radius.\"\n\nThis skill is the Infrastructure-as-Code counterpart to `ywc-code-gen`: it turns an infrastructure design into working Terraform, dispatches per-module authoring to a Codex worker carrying the `ywc-cloud-engineer` persona (single-responsibility infra worker — the infra counterpart to `ywc-backend-coder`), verifies with `terraform validate` \u002F `terraform plan`, and reports a blast-radius summary before anything is applied. **Terraform is the single fixed IaC tool for this toolkit** — Kubernetes and Helm resources are expressed through the Terraform `kubernetes` \u002F `helm` providers, never raw manifests, a standalone Helm chart, or a second IaC tool (Pulumi \u002F CDK \u002F CloudFormation \u002F Bicep).\nThis skill is the Infrastructure-as-Code counterpart to `ywc-code-gen`: it turns an infrastructure design into working Terraform inside the current Codex session, uses the read-only `ywc-cloud-engineer` persona for feasibility and blast-radius advisory where helpful, verifies with `terraform validate` \u002F `terraform plan`, and reports a blast-radius summary before anything is applied. **Terraform is the single fixed IaC tool for this toolkit** — Kubernetes and Helm resources are expressed through the Terraform `kubernetes` \u002F `helm` providers, never raw manifests, a standalone Helm chart, or a second IaC tool (Pulumi \u002F CDK \u002F CloudFormation \u002F Bicep).\n\n## Rationalization Defense\n\nWhen tempted to bypass a rule, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"No `infra-design.md` exists — I'll just infer the topology and start writing Terraform\" | Inferring topology duplicates `ywc-infra-design`'s decision and compounds the error downstream. Either ask the user to run `$ywc-infra-design` first, or explicitly clarify inline intent (service list, provider, network boundary) and record it before authoring — never guess silently. |\n| \"`terraform plan` looks safe, I'll run `apply` to confirm it actually works\" | `apply` mutates live infrastructure and is irreversible for destroy operations. This skill and its worker stop at `plan`; `apply` requires explicit human approval outside this skill's scope. |\n| \"Kubernetes work is easier as a raw manifest or a Helm chart\" | Terraform is fixed as the single IaC tool for this toolkit. K8s\u002FHelm resources go through the Terraform `kubernetes` \u002F `helm` providers so the same validate\u002Fplan\u002Fstate discipline applies uniformly — raw manifests and standalone Helm bypass that discipline. |\n| \"I'll hardcode the DB password as a default so `plan` runs cleanly\" | Hardcoded secrets leak into `.tf` files, version control, and Terraform state (which itself must never be committed). Route sensitive values through variables, `TF_VAR_*`, or a secret manager reference. |\n| \"Terraform state is only local for now, I'll commit it so the next run skips `init`\" | `*.tfstate` and `*.tfstate.backup` can contain plaintext secrets and resource IDs; committing them is a leak, not a convenience. Use a remote backend with locking (S3+DynamoDB, GCS, azurerm, Terraform Cloud) and gitignore state files. |\n| \"The plan output is long, I'll just say 'a few resources change'\" | The blast-radius summary must report the exact add\u002Fchange\u002Fdestroy counts and name every destroy against a stateful resource (DB, bucket, volume) explicitly — vague summaries hide data-loss risk from the reviewer. |\n| \"This is a tiny IaC change, I'll skip recommending `ywc-infra-review`\" | Even small Terraform diffs can widen a security group or loosen an IAM policy. Recommending `$ywc-infra-review` after authoring is not optional ceremony — it is the pre-apply safety net this skill hands off to. |\n\n**Violating the letter of these rules is violating the spirit.** An IaC authoring pass that skips validate\u002Fplan discipline or applies without review turns a code review problem into a production incident.\n\n## Arguments\n\n| Parameter | Format | Example | Description |\n|-----------|--------|---------|-------------|\n| `--design-doc` | `--design-doc \u003Cpath>` | `--design-doc infra-design.md` | Path to the `ywc-infra-design` output to load as the authoring input. Omit to fall back to inline intent clarification (Step 1). |\n| `--scope` | `--scope \u003Cmodule-path>` | `--scope infra\u002Fmodules\u002Fnetwork` | Restrict authoring to a single Terraform module. Default: every module implied by the design input. |\n| `--skip-review-recommendation` | flag | `--skip-review-recommendation` | Skip the closing `ywc-infra-review` recommendation. Only valid when the upstream caller already schedules review itself. |\n\n## Workflow\n\n### Step 1: Load the design input, or clarify inline intent\n\nIf `--design-doc` is provided or an `infra-design.md` (the `ywc-infra-design` output contract) exists in the working context, load it as the authoring source of truth: service list, network topology, IAM boundaries, data stores, and the reliability\u002Fcost\u002Fsecurity trade-off notes it recorded.\n\nIf no design input exists, do not infer the topology. Clarify inline with the user: target provider (AWS\u002FGCP\u002FAzure\u002FK8s), the services\u002Fresources involved, and any network or IAM constraints — then record that intent before moving to Step 2. For anything beyond a small, well-understood change, recommend the user run `$ywc-infra-design` first.\n\n### Step 2: Load the fixed IaC tool reference\n\nRead `..\u002Freferences\u002Finfra\u002Fiac\u002Fterraform.md` — the canonical `fmt → init → validate → plan → (human approval) → apply` workflow, blast-radius reporting shape, and state-management guards. This is the only IaC-tool reference this skill loads; Terraform is fixed and no other IaC tool reference exists in this toolkit.\n\nLoad the provider-specific reference matching the design's target provider — only the one file needed, per Progressive Disclosure:\n\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Faws.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fgcp.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fazure.md`\n- `..\u002Freferences\u002Finfra\u002Fproviders\u002Fk8s.md` — Kubernetes\u002FHelm via the Terraform `kubernetes`\u002F`helm` providers\n\n### Step 3: Author per Terraform module with optional advisory consult\n\nFor each Terraform module implied by the design (network, compute, data store, IAM, etc.), or a single narrowed pass when `--scope` targets one module, author the `.tf` files in the current Codex session. When provider-specific feasibility, reliability, or blast-radius judgment is unclear, consult the read-only `ywc-cloud-engineer` persona with the relevant slice of the design input and the matching provider reference from Step 2. That consult is advisory only: it does not author files, run `terraform apply`, or replace the main session's ownership of the Terraform edits.\n\n### Step 4: Verify — `terraform validate` \u002F `terraform plan`\n\nConfirm each authored module returned a clean `terraform validate` and a completed `terraform plan` (per the terraform.md verification workflow). If an advisory consult returns `BLOCKED` or `NEEDS_CONTEXT` (missing design input, unresolved provider constraint, blast-radius ambiguity), surface it rather than papering over it with a guess.\n\n### Step 5: Blast-radius summary\n\nAggregate every module's `plan` headline into one summary: total resources to add \u002F change \u002F destroy, with every destructive change against a stateful resource (database, bucket, volume, persistent disk) called out explicitly. See Output Format below for the exact shape.\n\n### Step 6: State handling and secret externalization guards\n\nBefore closing out, confirm:\n\n- No `*.tfstate` \u002F `*.tfstate.backup` \u002F `.terraform\u002F` was staged or committed.\n- No `.tfvars` file containing a literal secret was staged or committed.\n- Every credential, password, or API key in the authored `.tf` files flows through a variable, `TF_VAR_*`, or a secret-manager data source — never a hardcoded default.\n- A remote backend with locking is configured (or already exists) for any module holding state that matters beyond a single local run.\n\n### Step 7: Recommend `ywc-infra-review`\n\nUnless `--skip-review-recommendation` was passed, close the authoring pass by recommending the user run `$ywc-infra-review` before `apply` — especially when the blast radius includes a security group, IAM policy, or public-exposure change.\n\n## Output Format\n\n```text\nIaC Authoring Report\n─────────────────────────────────────────────────\nDesign input:    infra-design.md  (or \"inline intent\" if none was provided)\nTool:            Terraform (single fixed tool)\nModules authored:\n  - infra\u002Fmodules\u002Fnetwork      (authoring in current session, advisory consult optional)  validate: PASS  plan: PASS\n  - infra\u002Fmodules\u002Fdata         (authoring in current session, advisory consult optional)  validate: PASS  plan: PASS\n\nBlast radius (aggregate):\n  Plan: 9 to add, 3 to change, 1 to destroy.\n  ⚠ destroy: aws_db_instance.legacy   (stateful — confirm backup\u002Fsnapshot before apply)\n\nState handling:\n  - No *.tfstate staged or committed\n  - Remote backend: S3 + DynamoDB (configured)\n\nSecrets:\n  - 0 hardcoded credentials found; DB password routed through TF_VAR_db_password\n─────────────────────────────────────────────────\nRecommended next step: $ywc-infra-review (before apply)\n```\n\n## Validation Checklist\n\nBefore declaring the authoring pass complete, verify:\n\n- [ ] The design input was loaded, or inline intent was explicitly clarified and recorded (never silently inferred)\n- [ ] Every dispatched module returned `terraform validate` PASS\n- [ ] Every dispatched module returned a completed `terraform plan` (no live `apply` executed)\n- [ ] The blast-radius summary names every destroy against a stateful resource\n- [ ] No `.tfstate` file and no literal secret in a `.tfvars` file was staged or committed\n- [ ] Every secret in authored `.tf` files flows through a variable or secret-manager reference\n- [ ] `$ywc-infra-review` was recommended, unless `--skip-review-recommendation` was passed by an upstream caller\n\n## Common Mistakes\n\n- **Re-deriving the topology instead of loading the design input.** When `infra-design.md` exists, use it verbatim — re-deriving from scratch risks drifting from the reviewed trade-offs (network CIDR choices, IAM boundaries) that design phase already settled.\n- **Treating the advisory consult as the authoring worker.** The `ywc-cloud-engineer` persona is read-only; it can clarify feasibility or blast radius, but the current Codex session owns the Terraform edits.\n- **Treating a `NEEDS_CONTEXT` return from the advisory consult as a prompt to guess and continue.** The consult returns `NEEDS_CONTEXT` specifically when the design decision it needs is missing — surface it to the user rather than filling the gap with an assumption.\n- **Skipping Step 6's state\u002Fsecret guard because `plan` already succeeded.** `terraform plan` succeeding says nothing about whether a secret is hardcoded or whether state got staged — that check is separate and mandatory every pass.\n\n## Integration\n\n- **Upstream**: `ywc-infra-design` (produces the `infra-design.md` input contract); direct user invocation with inline intent when no design phase is warranted.\n- **Downstream**: `ywc-infra-review` (recommended after every authoring pass, mandatory before `apply` when the blast radius touches security\u002FIAM\u002Fpublic exposure).\n- **Pairs with**: `ywc-cloud-engineer` persona (the read-only specialist that advises on feasibility, reliability, and blast radius while this skill authors the Terraform).\n- **Must not be paired with**: authoring a second IaC tool in the same change (Pulumi\u002FCDK\u002FCloudFormation\u002FBicep\u002Fstandalone Helm) — Terraform is fixed.\n\n## References\n\n| Reference | Use when |\n|---|---|\n| `..\u002Freferences\u002Finfra\u002Fiac\u002Fterraform.md` | Every authoring pass — the fixed tool's verification workflow, blast-radius reporting shape, and state guards |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Faws.md` | Design's target provider is AWS |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fgcp.md` | Design's target provider is GCP |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fazure.md` | Design's target provider is Azure |\n| `..\u002Freferences\u002Finfra\u002Fproviders\u002Fk8s.md` | Design's target includes Kubernetes\u002FHelm (via Terraform providers) |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Fsecurity.md` | Spot-checking for an obvious misconfiguration (public bucket, open security group) while authoring, ahead of the full `ywc-infra-review` pass |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Fcost.md` | Flagging an obviously oversized resource while authoring, ahead of `ywc-infra-optimize` |\n| `..\u002Freferences\u002Finfra\u002Flenses\u002Freliability.md` | Confirming a new module has basic redundancy\u002Fbackup coverage before handing off to review |\n",{"name":5,"description":7},"main","7e8ac872e53df8c89d75663e031626281a2a2f5c","plugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author",1,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fyongwoon","https:\u002F\u002Fwww.webhani.com","2026-11-08 17:14:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-iac-author",{"tool":37,"command":38},"bunx","bunx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-iac-author",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-iac-author","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",302,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"README.en.md",2765,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FREADME.en.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"README.ja.md",2935,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FREADME.ja.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"README.ko.md",2799,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FREADME.ko.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"README.md",2782,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-iac-author\u002FREADME.md",[68,74,80,87,94,101],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72TQ84GTCPCV2VJ778V17TW","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72TQ6M4BFWE7P9EPW0GZDCM","malformed-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmalformed-frontmatter\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72TQ3ESGKXZ4QRWGTX92BKJ","fixture-501-fail","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F501-fail\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72TQ0HJ8H3R37J9WPWGKJZR","fixture-500-pass","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F500-pass\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M72TPWNCC7NEYD0D9N12KSQS","ywc-worktrees","(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: \"worktree 생성\", \"worktree audit\", \"worktree 정리\", \"worktree prune\", \"ywc-worktrees\", \"create worktree\". Do not use for branch creation\u002Fdeletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-worktrees\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M72TPRNR3E6QWB91GM98ABBV","ywc-wayfinder","(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: \"wayfinder\", \"길찾기\", \"discovery map\", \"multi-session discovery\", \"탐색 ticket\", \"経路整理\", \"探索マップ\", \"ywc-wayfinder\". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker\u002Fdatabase writes outside the local Markdown map.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-wayfinder\u002FSKILL.md",[],[]]