Issue-Driven GitHub Flow

This skill encodes a disciplined development workflow: nothing gets coded until a GitHub issue exists and a plan for it has been reviewed and approved. The goal is that every line of code is traceable to a tracked, planned, and reviewed unit of work — which keeps main clean, history meaningful, and review load low.

The workflow has two layers that always apply together:

1. The gitflow — how branches, commits, PRs, CI gates, and rollback are shaped (mechanical, fast).
2. The orchestration — how an issue becomes a reviewed plan, reviewed code, and then a human-approved merge using distinct agent roles.

The non-negotiables (and why)

These few rules are what make the workflow trustworthy. Everything else is mechanism in service of them.