GitHub Goal Delivery

Use GitHub as the required durable coordination layer for a long-running goal. This skill requires a GitHub remote plus issue and PR access; if those are unavailable, record the blocker and ask for access rather than adapting to another tracker. Prefer the gh CLI for issue and PR operations; use another available GitHub interface only when gh is unavailable.

Principles

• The user's overall objective is the goal; GitHub is the durable state that survives handoffs.
• One issue should be one independently implementable unit of work.
• Issues are context delivery. A fresh agent should be able to implement an issue without hidden chat history; links supplement context but do not replace it.
• PRs are the reviewer interface. An issue is not done until its PR has passed independent review and merged.
• Keep PRs small enough to review deeply. Split or re-scope work that becomes diffuse. Before opening a PR, sanity-check size along two axes: volume, such as roughly 500+ changed lines a reviewer must reason about (count production code and tests; discount generated code, lockfiles, snapshots, golden files, and bulk fixtures), and spread, such as changes across many files or ownership boundaries. Either axis is a signal to reconsider splitting the issue. When a PR is unavoidably large or cross-cutting, say so explicitly in the reviewer notes and widen the review panel rather than letting a big diff get a thin review.
• Keep the progress tracker issue authoritative: current plan, shared context, issue checklist, and final status.
• Do not add backward compatibility unless explicitly required by the user or tracker. Avoid shims, legacy framing, and constraints for hypothetical old integrations; correct stray wording when it does not change behavior.
• Be willing to pursue a large goal when the plan is sound. Prefer the cohesive, modern solution over timid incremental patches; confidence must come from repo context, validation, and review.

Templates

Load references/templates.md when creating or updating the progress tracker, implementation issues, or PR descriptions.