completion-check

When building infrastructure, verify it's actually connected to the system before marking as complete. Infrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort. Trace the execution path - Follow from user intent to actual code execution: Check hooks are registered , not just implemented: Verify database connections - Ensure infrastructure uses the right backend: Test end-to-end - Run the feature and verify infrastructure is invoked: Search for orphaned implementations : Before declaring infrastructure complete: Wrong approach: Right approach: - Trace the execution path - Follow from user intent to actual code execution: # Example: Verify Task tool spawns correctly grep -r "claude -p" src/ grep -r "Task(" src/ - Check hooks are registered , not just implemented: # Hook exists? ls -la .claude/hooks/my-hook.sh # Hook registered in settings? grep "my-hook" .claude/settings.json - Verify database connections - Ensure infrastructure uses the right backend: # Check connection strings grep -r "postgresql://" src/ grep -r "sqlite:" src/ # Should NOT find if PostgreSQL expected - Test end-to-end - Run the feature and verify infrastructure is invoked: # Add debug logging echo "DEBUG: DAG spawn invoked" >> /tmp/debug.log # Trigger feature uv run python -m my_feature # Verify...