Arrive Advance Draft

• Objective: What problem are we solving? (from user's stated goal)
• Behavioral Change: What will be different after this change?
• Implementation Tasks: Break down the work (if not already done)
• Risk + Rollback: Identify risks and how to revert
• Evidence: What tests/verification will be done?

Drafting Guidelines

Objective

• One sentence explaining WHY this change exists
• Focus on the problem being solved, not the solution

Behavioral Change

• Describe what's different AFTER this change ships
• Use "After this advance:" bullet format
• Be specific about observable changes

Implementation Tasks

• Break into logical phases
• Include tidying, testing, and feature work
• Mark completed items as done

Risk + Rollback

• Identify what could go wrong
• Describe how to undo the change
• Note any dependencies or migration concerns

Evidence

• List verification methods
• Include test types (unit, integration, manual)
• Note any TDD/Tidy First practices used

Expected Output Format

📝 Advance Draft

Created/Updated: arrive/systems/[system]/advances/ADV-[COMPONENT]-NNN.md

Summary:
├─ ID: ADV-[COMPONENT]-NNN
├─ Title: [descriptive title]
├─ System: [system-id]
├─ Components: [list]
└─ Score: XX [LEVEL]

Sections:
✓ Objective - [summary]
✓ Behavioral Change - [N bullet points]
✓ Implementation Tasks - [N tasks]
✓ Risk + Rollback - [identified]
✓ Evidence - [N items]

💡 Review the advance file and refine as needed.