Github Issue Workflow

This is an opinionated, security-first workflow that takes you from a GitHub issue number to a merged PR in eight structured phases. It forces you to confirm requirements before writing code, treats issue bodies as untrusted content to avoid prompt injection, and won't let you skip the boring parts like running tests and code review. The workflow uses gh CLI, spins up sub-agents for exploration and review, and gates you at Phase 2 and Phase 4 with mandatory confirmations. If you tend to jump straight into coding when someone says "fix issue 42," this will slow you down in a good way. Best for teams that want consistency and guardrails, less so if you prefer freeform problem solving.