Snap Plan

Read a GitHub issue → identify durable decisions → draft tracer-bullet phases → post as issue comment. Issue-type agnostic — works on PRDs or individual slices; plan depth scales to issue scope.

1. Get the issue

If issue URL/number in conversation context, use it. Otherwise ask. Fetch with gh issue view <number>.

2. Explore codebase

Understand current architecture, existing patterns, integration layers. Focus on what's relevant to the issue — module boundaries, dependency graphs, test infrastructure.

Use subagents for deep exploration of unfamiliar areas.