AI Agent Workflow Collection

Create and execute a durable, git-tracked Goal Ledger for multi-phase or long-running work: .goal-ledger/GOAL.md plus phase-NNNN.md files, plan and execution approval gates, an isolated goal branch recommendation, committed recovery markers, inter-agent handoff state, and optional safe squashing on acceptance. Use when work needs several distinct phases, may span sessions, needs crash recovery or handoff, or the user asks for a persistent goal, execution ledger, or durable plan. Sections 1-3 are the shared contract used by the goal-ledger-resume, goal-ledger-status, and goal-ledger-abandon skills.

Mark the current Goal Ledger abandoned while preserving its files and Git history for recovery and audit. Use only when the user explicitly asks to abandon, cancel, or scrap the active goal. Never delete .goal-ledger, reset commits, discard code, delete a branch, or treat a blocked goal as abandoned without explicit confirmation.

Resume and recover an unfinished Goal Ledger after interruption, a crash, context compaction, or agent handoff. Reconcile .goal-ledger files with the recorded branch, immutable baseline, Goal-ID commit trail, dirty worktree, and committed phase-start markers; verify uncertain work, repair bookkeeping, and continue execution. Use when .goal-ledger/GOAL.md is unfinished, the user says resume or continue the goal, or ledger and Git state may disagree.

Produce a strictly read-only status and handoff report for the current Goal Ledger, including phase progress, next action, blockers, Git strategy, matching Goal-ID commits, branch or baseline inconsistencies, foreign commits, and dirty crash evidence. Use when the user asks for goal status, where the work stands, what remains, or an inter-agent handoff summary. Never modify files, commits, branches, or statuses.