Documentation Generator MCP Server

{ "status": "deferred", "last_updated": "2025-10-14", "overview": "Features deferred from initial workorder tracking implementation. These enhancements would build on the foundation of 1:1 workorder-to-plan relationship.", "deferred_features": [ { "id": 1, "name": "Multiple Workorders Per Plan", "status": "deferred", "description": "Allow a single plan to contain multiple workorders for complex features with distinct sub-features", "use_case": "Single plan file with WO-AUTH-001 (Login), WO-AUTH-002 (Registration), WO-AUTH-003 (Password Reset)", "why_deferred": [ "Adds complexity to validation and tracking", "Most plans should stay focused (1:1 keeps plans manageable)", "If feature is too large, better to split into multiple plan files" ], "future_implementation": [ "Add workorder_tracking.max_workorders setting", "Update validator to handle multiple workorders", "Update reporting to show progress across workorders within plan" ] }, { "id": 2, "name": "Nested Workorders (Sub-Workorders)", "status": "deferred", "description": "Allow workorders to have sub-workorders for deeply hierarchical features", "use_case": "WO-AUTH-001 containing WO-AUTH-001-A (Login), WO-AUTH-001-B (Registration), WO-AUTH-001-C (Password Management)", "why_deferred": [ "Significant complexity increase", "Unclear if needed given 1:1 plan-to-workorder model", "Can achieve similar organization with multiple flat workorders" ], "future_implementation": [ "Add parent_workorder_id field to workorder schema", "Update validator for nested dependency validation", "Add depth limit (e.g., max 2 levels deep)" ] }, { "id": 3, "name": "Multi-Plan Progress Rollup", "status": "deferred", "description": "Track progress across multiple related plans as part of larger initiative", "use_case": "Project 'E-Commerce Platform' with auth-plan.json (100%), products-plan.json (60%), checkout-plan.json (0%) showing overall 53% complete", "why_deferred": [ "Requires cross-plan tracking infrastructure", "Need to define 'project' concept (group of plans)", "Can manually track for now" ], "future_implementation": [ "Add project_id field to plan metadata", "New MCP tool: generate_project_report(project_id)", "Project manifest file listing all related plans", "Dashboard view showing all plans in project" ] }, { "id": 4, "name": "Team Assignment Features", "status": "deferred", "description": "Assign workorders to specific team members or AI agents for collaboration", "use_case": "WO-AUTH-001 assigned to developer-1, status in_progress, with timestamps", "why_deferred": [ "Current workflow is solo/AI-driven", "Team features require user/agent identity system", "Need collaboration primitives first" ], "future_implementation": [ "Add assigned_to, assigned_at, assigned_by fields", "Add workorder status transitions (pending → assigned → in_progress → review → complete)", "New MCP tools: assign_workorder, get_my_workorders", "Integration with team management systems" ] }, { "id": 5, "name": "Dependency Visualization", "status": "deferred", "description": "Generate visual dependency graphs showing workorder relationships", "use_case": "Graph showing WO-AUTH-001 (complete) → WO-SESSION-001 (in_progress) → WO-DASHBOARD-001 (pending)", "why_deferred": [ "Visualization requires rendering infrastructure", "Textual dependency validation sufficient for MVP", "Most plans have simple linear dependencies" ], "future_implementation": [ "Generate Mermaid/DOT graph from workorder dependencies", "Highlight critical path", "Show blocked workorders (dependencies not met)", "Export to SVG/PNG for documentation" ], "tools": [ "Mermaid.js for graph rendering", "GraphViz DOT format support", "Critical path analysis algorithm" ] } ], "implementation_priority": { "v2.0_high_priority": [ "Multi-plan progress rollup (most requested by users)", "Workorder status transitions (in_progress, blocked, etc.)" ], "v2.1_medium_priority": [ "Dependency visualization (nice-to-have for complex projects)", "Multiple workorders per plan (if user feedback demands it)" ], "v3.0_low_priority": [ "Team assignment features (only if collaboration use case emerges)", "Nested workorders (only if proven necessary)" ] }, "decision_criteria": { "description": "Before implementing any deferred feature, validate:", "criteria": [ { "name": "User demand", "requirement": "Has feature been requested by 3+ users?" }, { "name": "Use case clarity", "requirement": "Do we have real-world examples where current approach fails?" }, { "name": "Complexity justification", "requirement": "Does benefit outweigh implementation complexity?" }, { "name": "Backward compatibility", "requirement": "Can it be added without breaking existing plans?" } ] }, "notes": [ "Focus MVP on 1:1 workorder-to-plan relationship", "If plans grow too large, guide users to create multiple focused plan files", "Prioritize simplicity and ease of use over feature completeness", "Let user feedback drive which enhancements to implement first" ] }