docs: add NEXT.txt with tomorrow's development plan

- Primary focus: validate tddai infrastructure robustness
- Plan to use tddai to test tddai itself (dogfooding)
- Ensure foundation is solid before building new features
- Include secondary opportunities for core MarkiTect development
- Set clear success criteria for infrastructure validation

Ready for tomorrow's session focused on testing and validation.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

NEXT.txt

@@ -0,0 +1,58 @@
+# Next Steps for MarkiTect Development
+
+**Session Goal for Tomorrow**: Test tddai infrastructure thoroughly using tddai itself to ensure robustness before proceeding with new features.
+
+## 🔧 **Primary Focus: Validate TDD Infrastructure**
+
+### 1. Self-Testing with tddai
+- Use `make tdd-start NUM=11` to test actual workspace creation with issue #11
+- Generate real tests using `make tdd-add-test` to validate AI integration
+- Complete full cycle: start → add-test → status → finish
+- Identify any rough edges or workflow issues
+- Ensure error handling works correctly for edge cases
+
+### 2. Infrastructure Robustness Testing
+- Test with invalid issue numbers
+- Test workspace collision scenarios (multiple active workspaces)
+- Test cleanup and recovery from failed states
+- Validate all error messages are helpful and actionable
+- Ensure virtual environment integration is solid
+
+## 🎯 **Secondary Opportunities (After Infrastructure Validation)**
+
+### 3. Core MarkiTect Feature Implementation
+- Pick a Markdown feature from wiki specs (MF-1 through MF-10)
+- Use the validated TDD workflow to implement it properly
+- Expand `markitect/parser.py` with real functionality
+- Demonstrate TDD infrastructure working with actual feature development
+
+### 4. CLI Interface Development
+- Build out the actual MarkiTect CLI described in architecture
+- Implement GraphQL interface and SQLite database integration
+- Make the project immediately useful for end users
+
+### 5. Schema Validation System
+- Implement JSON Schema validation features (core differentiator)
+- Build schema generation from existing Markdown
+- Add validation and stub generation capabilities
+
+### 6. Integration & Polish
+- Set up actual CI/CD pipeline
+- Add code coverage reporting with pytest-cov
+- Implement proper linting/formatting targets (black, ruff, mypy)
+- Performance optimization and documentation improvements
+
+## 📋 **Success Criteria for Tomorrow**
+
+**Primary Goal**: Confidently say "the TDD infrastructure is robust and reliable"
+- Complete issue #11 workflow without major issues
+- Generate and run meaningful tests via the tddai system
+- Document any improvements or fixes needed
+- Ready to use tddai for implementing new MarkiTect features
+
+**Philosophy**: Validate the foundation before building the house. Any problems we encounter should be attributable to new feature implementation, not infrastructure issues.
+
+---
+
+*Created: 2025-09-22*
+*Next Session: Focus on self-testing and validation of tddai infrastructure*