code-oz

Use to think through a feature's design, requirements, and trade-offs before building — advisory exploration, not an enforced gate.

Use to plan a RED-first TDD ordering for a behavior change — advisory test-ordering guidance, not an enforced gate.

Use to verify spec, reference code, and library docs before writing code — advisory guidance on the 3-source discipline, not an enforced gate.

Drive the code-oz agentic SDLC runtime to build or fix code with enforced gates and cross-family review. Use when the user asks to build, implement, or fix something in a code repository and wants gated, reviewed delivery rather than ad-hoc edits.