tegwick
cbde1dabc4
Create detailed 26-week workplan for Prompt Dependency Resolution system implementing all 11 functional requirements across 8 phases: - Phase 1-2: Foundation (artifacts, templates, macros) - Phase 3-4: Resolution and execution engine with idempotent runs - Phase 5-6: Dependency tracking and incremental recomputation - Phase 7-8: Quality validation and observability/traceability Includes database schemas, verification strategies, risk management, and complete file structure for ~60 new modules. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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