stubbing-temporary-comments

You can plan code changes by inserting structured STUB blocks at intended implementation sites to map out logic before writing the real code. This two-pass workflow uses a Recon Pass to map changes and a Stub Pass to insert markers.

The two-pass stubbing workflow separates planning from implementation by first mapping changes with structured STUB markers, then replacing those markers with working code in a second pass to ensure organized code refactoring.

To make code planning comments survive into final implementation, use structured STUB blocks with IN, OUT, and EDGE markers to capture intent and requirements, ensuring rationale is preserved during the second implementation pass.

Yes, this comment-first coding approach is specifically designed for complex multi-file features and refactors with uncertain details, allowing you to place STUB blocks across files before implementing the real logic.

You can verify all temporary code planning markers are resolved by using the built-in cleanup and quality checks that enforce a DONE criterion, ensuring no unresolved STUB markers remain in the final code.