Files

tegwick 72519bf83d chore: close release-management-optimization topic

- Move topic from roadmap/ to history/
- Add DONE.md with comprehensive completion summary
- Topic fully complete with all 9 optimizations implemented
- Exceeded original scope (Stages 1-2 + all of Stage 3)
- Ready for archive

2026-01-06 22:54:10 +01:00

eat-the-frog

chore: roadmap cleanup

2026-01-05 20:37:18 +01:00

README.md

docs: standardize on yymmdd- timestamp prefix format

2026-01-06 03:57:42 +01:00

README.md

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