tegwick
c5f49b2dd0
Replace NEXT.md approach with standardized Keep a Todofile V0.0.1 format for better task management and human-AI collaboration during coding sessions. ## Todofile System Setup: - **TODO.md**: Main todofile following Keep a Todofile V0.0.1 format - **TODOFILE_GUIDE.md**: Comprehensive system documentation and workflow - **Integration**: Fully integrated with existing kaizen-agentic framework - **Agent Support**: Uses agent-keepaTodofile for maintenance ## Content Migration: - Migrated strategic priorities from NEXT.md to TODO.md [Unreleased] section - Preserved session success criteria and development milestones - Organized tasks by impact type (To Add, To Fix, To Refactor) - Archived NEXT.md to history/NEXT_archived_20251025.md ## Documentation Updates: - README.md: Updated "Next Actions" → "Current Tasks" link - agent-project-management.md: Updated workflow to use TODO.md - docs/README.md: Updated project management references - Added comprehensive TODOFILE_GUIDE.md ## Benefits: - **Standardized Format**: Industry-standard Keep a Todofile format - **Better Organization**: Impact-based task categorization - **AI-Ready**: Designed for human-AI collaboration workflows - **Context Preservation**: Maintains coding flow across session interruptions - **Integration Ready**: Works with existing agent and capability systems Active tasks now in TODO.md [Unreleased] section focusing on strategic issue resolution and capability management validation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| architecture | ||
| cost-analysis | ||
| development | ||
| integration | ||
| manuals | ||
| user-guides | ||
| advanced_packaging.md | ||
| agents | ||
| ASSET_MANAGEMENT_USER_GUIDE.md | ||
| CLI_TUTORIAL.md | ||
| graphql_interface.md | ||
| markitect.1 | ||
| md-explode-command.md | ||
| README.md | ||
| search.md | ||
| wishlist.md | ||
MarkiTect Documentation
Welcome to the MarkiTect documentation. This directory contains comprehensive documentation for developers, users, and contributors.
Documentation Structure
📐 Architecture Documentation (architecture/)
Deep technical documentation about system design, performance, and implementation details.
- Caching System - Why and how MarkiTect's AST caching delivers 60-85% performance improvements
- Coming soon: Database Schema, CLI Architecture, Plugin System
👥 User Guides (user-guides/)
End-user documentation for working with MarkiTect CLI and features.
- Coming soon: Getting Started, Command Reference, Best Practices
🔧 Development Documentation (development/)
Documentation for contributors and developers extending MarkiTect.
- Coming soon: Contributing Guide, Testing Strategy, Release Process
Quick Links
For Users
- Installation & Setup
- Command Reference (coming soon)
- Performance Guide (coming soon)
For Developers
- Architecture Overview - System design and component relationships
- Development Setup - Local development environment
- API Documentation (coming soon)
Project Management
- Project Status - Current development status
- Roadmap - Strategic development plan
- Current Tasks - Task management using Keep a Todofile format
Key Concepts
Core Architecture Principles
- Parse Once, Use Many Times - AST caching for 60-85% performance improvement
- Convention Over Configuration - Sensible defaults with minimal setup
- Schema-Driven Processing - Structured markdown with validation
- Relational Metadata - Database-powered document relationships
Performance Philosophy
MarkiTect treats markdown documents as structured, queryable data rather than plain text. This approach enables:
- Lightning-fast document processing through intelligent caching
- Complex querying and relationship management
- Schema validation and consistency enforcement
- Scalable performance that grows with your content
Contributing to Documentation
Documentation follows the same quality standards as code:
- Clear Structure - Logical organization and navigation
- Practical Examples - Real-world usage patterns
- Performance Context - Why architectural decisions matter
- User-Focused - Written for the intended audience
Documentation Standards
- Use clear, concise language
- Include practical examples
- Explain the "why" behind design decisions
- Keep technical accuracy as the highest priority
- Update docs when changing functionality
This documentation is maintained alongside the codebase. For the most current information, always refer to the latest version in the repository.