tegwick
bf4767d06b
Added critical optimization #1 based on v0.10.0 release experience: **Issue**: git status doesn't show unpushed tags, leading to forgotten tag pushes **Impact**: v0.9.0 and v0.10.0 tags weren't pushed, plus older version tags **Solution**: Enhanced release status or git hook to show unpushed tags Total optimizations identified: 9 (was 8) - High Priority: 4 (added unpushed tags visibility) - Medium Priority: 3 - Low Priority: 2 Ready to implement all optimizations systematically.
MarkiTect Project Roadmap
This roadmap directory contains planning directories for roadmap topics.
- When starting to implement a topic its directory will be timestamped
- If implementing multiple topics in parallel use branches
- Keep current state of what's next to implement in TODO.md
- See ../history directory for closed topics
Naming Convention
Directory Format: yymmdd-topic-name
- Use 2-digit year prefix (e.g.,
260106-for 2026-01-06) - Lowercase topic names with hyphens
- Examples:
260106-semantic-document-validation,260105-schema-evolution
This convention keeps names concise while maintaining chronological sorting.
Purpose
This planning documentation serves multiple purposes:
- Implementation State Awareness: Allow for recovery after breaks or breakdowns
- Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
- Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
- Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized
xxx