aget-wind-down

name	aget-wind-down
description	End AGET session with state capture and sanity checks
allowed-tools	["Bash","Read","Write","Glob"]

aget-wind-down

End an AGET agent session properly. This skill runs the wind-down protocol to capture session state, run sanity checks, and prepare handoff notes.

Instructions

When this skill is invoked:

1. Run the wind-down script:

   python3 scripts/wind_down.py
   

2. The script will:

   • Run sanity checks (housekeeping protocol)
   • Capture session duration and activity
   • Scan for pending work in planning/
   • Generate session summary
   • Suggest commit message if changes exist

3. If user provides notes, pass them to the script:

   python3 scripts/wind_down.py --notes "User provided notes here"
   

4. Create session record file at sessions/SESSION_YYYY-MM-DD_descriptive_title.md:

   • Use YAML frontmatter with Session Metadata Standard v1.0 fields (date, duration_minutes, objectives, outcomes)
   • Include optional fields: learnings, commits, files_changed, pain_points, next_steps
   • Add session body sections: Objectives, Deliverables, Outcomes, Lessons, Blockers, Files Changed
   • Capture wind-down state in the file: sanity result, pending work, git diff stats
   • Reference schema: .aget/schemas/session_metadata_v1.0.yaml
   • Reference exemplar: sessions/SESSION_2025-12-03_kb_enhancement.md

5. If re-entrancy guard blocks (exit code 4), inform user:

   • Wind-down was run recently (5-minute cooldown)
   • Use --force to bypass if needed

Required Outputs

Every wind-down must produce:

1. Terminal summary (stdout) — sanity, changes, pending, suggested commit
2. Session record file — sessions/SESSION_YYYY-MM-DD_*.md (L004: process governance)

Output Format

Present the wind-down summary:

Wind Down Complete
- Session: [duration]
- Sanity: [healthy/warnings/errors]
- Pending: [N] items in planning/
- Changes: [staged/unstaged counts]
- Suggested commit: "[message]"

Error Handling

• Exit code 0: Clean close, sanity healthy
• Exit code 1: Close with warnings (report them)
• Exit code 2: Close with errors (require acknowledgment)
• Exit code 3: Configuration error
• Exit code 4: Re-entrancy guard active

Options

• --skip-sanity: Skip sanity check (not recommended)
• --force: Bypass re-entrancy guard (L468)
• --json: Machine-readable output

Related

• L004: Process Governance Gap (session file as required output)
• L468: Re-entrancy Protection
• L532: Skills vs Learnings Distinction
• CAP-SESSION-003: Wind Down Protocol