Goal to Release

Turn broad goals into issue-backed, reviewable, verified releases. Own sequencing, evidence, review hygiene, and closeout. Route concrete domain work to narrower skills instead of duplicating their mechanics.

Operating Model

Use live evidence first: repo instructions, worktree, branch, open issues, PRs, review threads, CI, deploy state, docs, scripts, and recent reviewer feedback. Treat memory and prompt history as leads to verify when facts can drift.

Keep a working goal ledger. Use working notes for short, single-PR work. Use a durable ledger by default when the goal spans multiple issues/PRs, stacked or parallel branches, repo-wide modernization, dependency upgrades, release orchestration, cross-session execution, or any user-requested handoff. Then use scripts/new_goal_ledger.py to create an isolated untracked goal directory. Read goal-ledger-lifecycle.md before creating, auditing, distilling, or handing off durable ledgers.