Completion Check: Verify Infrastructure Is Wired When building infrastructure, verify it's actually connected to the system before marking as complete. Pattern 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. DO 1. Trace the execution path Follow from user intent to actual code execution: 2. Check hooks are registered , not just implemented: 3. Verify database connections Ensure infrastructure uses the right backend: 4. Test end to end Run the feature and verify infrastructure is invoked: 5. Search for orphaned implementations : DON'T Mark infrastructure "complete" without testing execution path Assume code is wired just because it exists Build parallel systems (Task tool vs claude p spawn) Use wrong backends (SQLite when PostgreSQL is architected) Skip end to end testing ("it compiles" ≠ "it runs") Completion Checklist Before declaring infrastructure complete: [ ] Traced execution path from entry point to infrastructure [ ] Verified hooks are registered in .claude/settings.json [ ] Confirmed correct database/backend in use [ ] Ran end to end test showing infrastructure invoked [ ] Searched for dead code or parallel implementations [ ] Checked configuration files match implementation Example: DAG Task Graph Wrong approach: Right approach: Source Sessions This session: Architecture gap discovery DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL

completion-check