niko-preflightlisted

# Preflight Phase - Pre-Build Plan Validation This command validates the implementation plan against codebase reality before any code is written. It catches design oversights, convention conflicts, TDD violations, and integration issues that would otherwise surface during or after the build. ## Step 1: Load Memory Bank Files Read: - `memory-bank/active/tasks.md` - `memory-bank/active/projectbrief.md` - `memory-bank/systemPatterns.md` - `memory-bank/techContext.md` - `memory-bank/active/creative/**/*.md` (if any exist) ## Step 2: Preflight Workflow 1. **Verify Prerequisites** - Check `memory-bank/active/tasks.md` for planning completion - For Level 3-4: Verify creative phase documents exist (if creative phases were flagged) - Read implementation plan and design decisions 2. **TDD Plan Encoding** *(blocking)* - The test-first process lives in `.cursor/rules/shared/always-tdd.mdc` - This check governs units that change executable behavior. A unit delivering user-facing prose or policy (docs content, PR/issue templates, CONTRIBUTING, instructional comments, rule/skill wording, etc.) owes no tests for those artifacts; omitting tests for those artifacts passes this check - For each implementable unit of executable work (function, slice, milestone — whatever granularity the plan uses), confirm the ordered substeps place test-writing before production code, explicitly enough that a reasonable implementer cannot follow the plan by coding first - When a numbe