Snap Forge — TDD Execute

Strict vertical TDD cycles. One test, one implementation, one commit. Refactor only after all behaviors green — premature refactoring reshapes code before you see the full picture (Ousterhout: patterns only emerge once enough implementation exists to reveal them).

1. Orient

Determine input: GitHub issue, conversation context, or direct task. Quick codebase scan of relevant area — detect test suite (package.json, pyproject.toml, Cargo.toml, go.mod, test dirs, CI config), existing patterns, test infrastructure.

If input is a GitHub issue, fetch comments via gh issue view <number> --comments. Look for a plan comment (## Durable Decisions or ## Phase headers). If found:

• Durable decisions are constraints — respect locked routes, schemas, models.
• Phase list defines the behavior sequence for TDD cycles.