Documentation Generator MCP Server

================================================================================ IDEA: DELIVERABLES_GENERATOR_MCP_TOOL ================================================================================ IDEA: DELIVERABLES_GENERATOR_MCP_TOOL DATE: 2025-10-15 23:15 STATUS: Ready for Planning DESCRIPTION: Create an MCP tool (Tool #24) that automatically generates DELIVERABLES.md files for any project. The tool analyzes git history, file system changes, and plan.json files to track what's been delivered across project phases with comprehensive metrics and status tracking. CONTEXT: The comprehensive-inventory-system project uses a DELIVERABLES.md file to track work across 6 phases with detailed metrics (code lines, files created, time spent). This pattern is valuable for any multi-phase project but requires manual creation and maintenance. By creating an automated MCP tool, we enable: - Every project to maintain professional deliverables documentation - Integration with the idea-logging workflow (idea → plan → deliverables) - Auto-discovery of phases from git history or plan files - Automatic metrics calculation from project artifacts RELATIONSHIP TO MCP: Tool #24 in docs-mcp ecosystem. Complements existing inventory tools: - Works with inventory_manifest (file-level details) - Integrates with create_plan (phase structure) - Consumes analyze_project_for_planning (context data) - Fits "project intelligence" category alongside other inventory/tracking tools - Enables complete project lifecycle: Idea → Analysis → Plan → Deliverables RELATED WORK: - coderef/future/idea-logging-workflow.txt (workflow template we're implementing) - coderef/future/DELIVERABLES.md (example DELIVERABLES.md template) - coderef/working/comprehensive-inventory-system/DELIVERABLES.md (real example) - Phase 5D: documentation_inventory tool (similar generator pattern to follow) - coderef/working/comprehensive-inventory-system/WORKFLOW-TRACKING.md (workflow docs) PRELIMINARY THOUGHTS: - Should follow generator pattern from Phase 5D (documentation_inventory) - Git parsing via gitpython to extract: commits, phases, branches, timelines - Phase detection: auto-detect from plan.json OR from git tags/commit messages - Metrics: aggregate file counts, lines of code, commit counts per phase - Template: render DELIVERABLES.md following coderef/future/DELIVERABLES.md structure - Must handle edge cases: new projects, no git history, manual phase definitions - Should integrate with existing constants/types (FileCategory, AnalysisDepth, etc.) - Consider performance: git history parsing could be slow on large repos - Metrics accuracy: use simple heuristics (LOC, file counts, commit dates) NEXT STEPS: - [ ] Analyze DELIVERABLES.md structure and extract common patterns - [ ] Review Phase 5D (documentation_inventory) implementation as reference - [ ] Create implementation plan (Phase 7A-7D breakdown) - [ ] Move to coderef/working/deliverables-generator/ when ready to implement - [ ] Archive to /archived/ when Tool #24 is shipped ================================================================================