Turn a completed Aurora openspec change into Diátaxis-structured documentation (concepts, guides, reference stubs) in both English and Spanish. Invoke after a change is archived in the source repo.
You have just archived (or plan to reflect) a feature in aurora-catalyst-cli (or another Aurora repo) and need to update the docs site. The archive lives at <cli-repo>/openspec/changes/archive/YYYY-MM-DD-<change-name>/.
You do NOT use this skill for:
scripts/import-from-sources.ts — running the script is enough.../aurora-catalyst-cli relative to this repo). Confirm with the user or use --add-dir / additionalWorkingDirectories.2026-04-18-preservation-regions).<cli-repo>/openspec/specs/<capability>/spec.mdIn this order:
<cli-repo>/openspec/changes/archive/<change>/proposal.md — the "why" and the scope (Impact section lists the files the change touched).<cli-repo>/openspec/changes/archive/<change>/design.md — architectural decisions and the rationale behind each.<cli-repo>/openspec/changes/archive/<change>/specs/<capability>/spec.md OR the canonical spec at <cli-repo>/openspec/specs/<capability>/spec.md — the normative requirements and scenarios.Do NOT read the tasks.md file in detail. It is implementation history; the design doc is a better source of "why".
Decide per-change which categories apply. Not every change needs all four.
Create or update src/content/docs/en/concepts/<topic>.md AND src/content/docs/es/concepts/<topic>.md.
Purpose: explain the why of the feature. Reader already knows Aurora exists; they want to build a mental model.
Template skeleton:
---