markitect-main/docs
tegwick 1d13cbb355 feat: implement feature wishlist system (issue #85)
Add comprehensive wishlist management for capturing and refining feature ideas:

• CLI Commands:
  - markitect wish create: Create new wishlist items with templates
  - markitect wish list: List and filter wishes by stage
  - markitect wish promote: Promote wishes through workflow stages
  - markitect wish convert: Convert ready wishes to regular issues

• Workflow Stages:
  - discussion: Initial idea capture and brainstorming
  - draft: Create specification and requirements
  - ready: Prepare for conversion to development issue
  - archived: Preserve ideas that won't be pursued

• Features:
  - Automatic label management (wish, wish/stage, priority/level)
  - Multiple output formats (table, simple, json)
  - Stage filtering and organization
  - Structured templates for each workflow stage
  - Comprehensive documentation and best practices

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-03 19:12:45 +02:00
..
architecture feat: Complete Issue #13 - Cache Management CLI Commands MAJOR MILESTONE 2025-09-25 23:03:03 +02:00
development feat: Complete Issue #13 - Cache Management CLI Commands MAJOR MILESTONE 2025-09-25 23:03:03 +02:00
integration feat: Integrate Requirements Engineering Agent and fix Issue #59 test failures 2025-10-02 00:45:06 +02:00
manuals feat: Complete test-fixing agent implementation and CLI consolidation 2025-10-03 01:48:03 +02:00
sub_agents feat: Complete Issue #57 - Testing efficiency optimization with TDD8 workflow enhancements 2025-10-02 05:11:25 +02:00
user-guides feat: Complete Issue #13 - Cache Management CLI Commands MAJOR MILESTONE 2025-09-25 23:03:03 +02:00
CLI_TUTORIAL.md chore: history cleanup 2025-10-03 03:39:43 +02:00
graphql_interface.md feat: implement GraphQL write interface with mutations (issue #10) 2025-10-03 16:48:03 +02:00
markitect.1 feat: Strategic pivot to CLI implementation with comprehensive foundation 2025-09-24 01:14:27 +02:00
README.md chore: cleanup of repository root 2025-10-03 02:38:06 +02:00
search.md feat: implement lightweight full text search plugin using SQLite FTS5 (issue #83) 2025-10-03 17:03:11 +02:00
wishlist.md feat: implement feature wishlist system (issue #85) 2025-10-03 19:12:45 +02:00

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

For Users

For Developers

Project Management

Key Concepts

Core Architecture Principles

  1. Parse Once, Use Many Times - AST caching for 60-85% performance improvement
  2. Convention Over Configuration - Sensible defaults with minimal setup
  3. Schema-Driven Processing - Structured markdown with validation
  4. 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:

  1. Clear Structure - Logical organization and navigation
  2. Practical Examples - Real-world usage patterns
  3. Performance Context - Why architectural decisions matter
  4. 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.