arrive-start

Detect development context and initialize an ARRIVE change session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new ARRIVE change session by detecting the current development context (branch, system, and potential advances) and preparing the session state.

Core Features & Use Cases

  • Detect branch and associated systems/components.
  • Identify existing planned advances and propose or create a new one.
  • Produce a session summary with started_at and next steps.

Quick Start

Run the ARRIVE start skill to initialize a new session from your current branch and repository state.

Frequently Asked Questions about arrive-start

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

FAQPage Schema
How do I start a change management session that detects my current git branch context?

To start a change management session, the skill auto-detects your current git branch and repository state, then initializes a new ARRIVE session by linking the branch, associated system, and planned advances.

What is an ARRIVE session in a development workflow?

An ARRIVE session is a structured change management process that records a deterministic started_at timestamp, links a specific advance to your current branch, and guides subsequent development steps.

How do I link a planned advance to my current development branch?

Linking a planned advance happens automatically when you run the session initialization, which identifies existing planned advances from your context and associates one with your current branch.

Can I initialize a deterministic workflow session without manually specifying the system and branch?

Yes, you can initialize a deterministic workflow session without manual input because the skill automatically detects your current branch, identifies associated systems, and prepares the session state.

What context does the session initialization detect from my repository state?

Session initialization detects your current git branch, identifies associated systems and components, finds existing planned advances, and produces a summary with started_at and next steps.

Does starting an ARRIVE session require any external dependencies?

Starting an ARRIVE session requires no external dependencies, running directly within your development workflow to detect repository context and initialize the change session state.