away

ADD Away Command v{{VERSION}}

The human is stepping away. Establish what work can proceed autonomously and what must wait.

Phase 1: Understand the Absence

Parse the duration from $ARGUMENTS. If not provided, default to 2 hours. Do not ask — just acknowledge the default: "No duration specified — I'll plan for a 2-hour session. Say /add:away 4 hours next time to adjust."

Phase 2: Assess Available Work

1. Read .add/config.json for autonomy level and environment tier
2. Re-read docs/prd.md to ground yourself in the project's objectives and scope — this keeps autonomous work aligned with the product vision
3. Scan specs/ for specs with status "Approved" or "Implementing"
4. Scan docs/plans/ for plans with status "Approved" or "In Progress"
5. Check current git status for in-progress work
6. Run TodoWrite to see current task list

Categorize Work

Autonomous (can do without human):

• Tasks with clear specs and plans where requirements are unambiguous
• Writing tests for specced features (RED phase)
• Implementing against existing failing tests (GREEN phase)
• Refactoring with test coverage (REFACTOR phase)
• Running quality gates and fixing lint/type errors
• Writing documentation for completed features
• Code review of existing PRs

Queued (needs human decision):

• Any task where the spec is ambiguous or missing
• Architecture decisions with multiple valid approaches
• Deployment to staging or production
• New feature specs (need interview)
• Dependency upgrades with breaking changes
• Anything that would benefit from a Decision Point

Phase 3: Present the Plan

Got it — you'll be away for approximately {DURATION}.

AUTONOMOUS WORK PLAN:
━━━━━━━━━━━━━━━━━━━
{numbered list of tasks, with spec references}

Estimated completion: {rough estimate}

QUEUED FOR YOUR RETURN:
━━━━━━━━━━━━━━━━━━━━━
{numbered list of decisions/tasks that need human input}

I'll maintain a work log and have a return briefing ready.

Phase 4: Get Confirmation