arrive-advance-draft

Draft ARRIVE Advance files with structured sections for system changes.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/srswart/good-control --skill arrive-advance-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arrive-advance-draft
Source: https://github.com/srswart/good-control/tree/main/.cursor/skills/arrive-advance-draft
Command: npx skills add https://github.com/srswart/good-control --skill arrive-advance-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting and updating ARRIVE Advance files to capture scope, risks, evidence, and timelines for changes.

Core Features & Use Cases

  • Generate new Advance drafts for proposed changes and update existing ones.
  • Enforce structured sections (Objective, Behavioral Change, Implementation Tasks, Risk + Rollback, Evidence) for reviewability.
  • Support review and collaboration by preserving user-added content while refreshing automatic sections.

Quick Start

Run arrive draft to create or update the Advance file for the current change.

Frequently Asked Questions about arrive-advance-draft

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

FAQPage Schema
What is an ARRIVE Advance file used for in change management workflows?

An ARRIVE Advance file documents scope, risks, evidence, and timelines for proposed system changes. It enforces structured sections like Objective, Behavioral Change, and Risk + Rollback to ensure governance compliance and reviewable change management.

How do I draft an ARRIVE Advance file for a current system change?

Run arrive draft to generate a new ARRIVE Advance file or update an existing one. The process captures implementation tasks, behavioral changes, and risk rollback plans while preserving any user-added content during automatic section refreshes.

What sections are required when documenting changes for ARRIVE governance review?

ARRIVE governance review requires structured sections including Objective, Behavioral Change, Implementation Tasks, Risk + Rollback, and Evidence. These sections capture change scope, track timestamps, and support collaborative review of system modifications.

Can I update an existing ARRIVE Advance draft without losing manually added content?

Updating an existing ARRIVE Advance draft preserves user-added content while refreshing automatic sections. This supports ongoing review and collaboration by maintaining manually entered scope details alongside generated timestamps and structured governance fields.

What's the best way to track risks and rollback plans in ARRIVE change management documentation?

Use the structured Risk + Rollback section within an ARRIVE Advance file to track risks and rollback plans. This ensures change management documentation captures evidence, timelines, and behavioral changes in a reviewable governance format.

When do I need to generate an ARRIVE Advance file for a proposed system change?

Generate an ARRIVE Advance file whenever proposing system changes that require governance review. The file captures scope, evidence, and timelines, fulfilling ARRIVE workflow requirements for reviewable and structured change management documentation.