coulomb/markitect-main
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
markitect-main/roadmap
History
tegwick eaf4a955af docs(roadmap): add workplan for extracting llm module as shared library 
3-stage plan: decouple (RunConfig/LLMResponse move + app name
parameterization) → extract to standalone package → adopt in first
consumer. Registered as workstream in Custodian State Hub.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-24 21:51:54 +01:00
..
260210-llm-integration feat(llm): add LLM integration module with OpenRouter and Claude Code adapters 2026-02-11 01:17:58 +01:00
eat-the-frog chore: roadmap cleanup 2026-01-05 20:37:18 +01:00
helper-command feat(helper): add interactive Q&A helper command 2026-02-12 23:28:20 +01:00
infospace-tooling docs: preliminary introduction to Viable Information Spaces 2026-02-18 23:54:53 +01:00
llm-shared-library docs(roadmap): add workplan for extracting llm module as shared library 2026-02-24 21:51:54 +01:00
prompt-dependency-resolution Included run manifest schema to check prompt dependency resolution against later 2026-02-09 20:38:07 +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:

  1. Implementation State Awareness: Allow for recovery after breaks or breakdowns
  2. Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
  3. Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
  4. Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized

xxx