arn-infra-document-change

Generate operational documentation from infrastructure change artifacts.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-infra-document-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-infra-document-change
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-infra/skills/arn-infra-document-change
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-infra-document-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Change management in infrastructure often generates scattered artifacts and manual notes. This skill automates the creation of comprehensive operational documentation from completed infrastructure changes, ensuring a single source of truth.

Core Features & Use Cases

  • Generate Runbooks, architecture updates, operational playbooks, environment docs, and changelog entries from change specs, plans, and execution reports.
  • Provide traceable, audit-ready documentation that aligns with IaC pipelines and project repositories.
  • Support multi-environment deployments and promote consistency across environments.

Quick Start

Trigger the documentation workflow by supplying the completed change artifacts and running the document-change process to generate all outputs.

Frequently Asked Questions about arn-infra-document-change

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

FAQPage Schema
How do I generate runbooks and architecture docs from infrastructure changes?

You can automate infrastructure documentation by feeding change specs, execution reports, and review reports into a documentation generator. This process reads completed change artifacts to produce runbooks, architecture updates, environment docs, and changelog entries automatically.

What is the best way to keep infrastructure documentation aligned with IaC pipelines?

To keep infrastructure documentation aligned with IaC pipelines, generate audit-ready docs directly from change specs and phase reports. This ensures your operational playbooks and changelog entries reflect the exact state of your deployment artifacts.

How do I create audit-ready operational documentation for multi-environment deployments?

Create audit-ready operational documentation for multi-environment deployments by processing completed change artifacts. The system validates input readiness and produces consistent environment docs and runbooks across all configured deployment targets.

What prerequisite artifacts do I need before automating infrastructure changelog generation?

Before automating infrastructure changelog generation, you need completed change artifacts including change specs, execution reports, and review reports. The workflow validates these input artifacts to ensure documentation production readiness before generating any outputs.

Can I use existing infrastructure change reports to update operational playbooks automatically?

Yes, you can use existing infrastructure change reports to update operational playbooks automatically. The system reads execution reports and change specs to produce comprehensive operational documentation in your configured Infra docs directory.

Why does my infrastructure documentation workflow fail to generate runbooks?

Infrastructure documentation workflows fail to generate runbooks when required change artifacts are missing. The system validates input readiness and requires completed change specs, execution reports, and review reports before producing any documentation outputs.