Documentation Generator MCP Server

{ "feature_name": "workorder-tracking", "description": "Add workorder IDs as plan identifiers, with each plan containing exactly one workorder that groups all related tasks. Workorder serves as a unique identifier for the plan and enables progress tracking.", "goal": "Provide clear plan identification and progress tracking by assigning each implementation plan a unique workorder ID (e.g., WO-AUTH-001) that serves as the parent identifier for all tasks within that plan", "requirements": [ "Every plan must have exactly ONE workorder (1:1 relationship)", "Workorder ID format: WO-FEATURE-NNN (e.g., WO-AUTH-001, WO-SESSION-001)", "All tasks in plan must reference the plan's workorder via workorder_id field", "Schema addition to planning standard (section 5: task_id_system)", "Plan validator updates to validate workorder format, task references, and dependencies", "New MCP tools: generate_workorder_report, update_workorder_status, get_workorder_tasks", "New slash commands: /workorder-report, /workorder-status, /workorder-tasks", "Auto-suggest workorder tracking in /create-plan (AI uses best judgment based on context)", "Integration with TodoWrite for hierarchical task display", "Workorder templates (reusable patterns for common features like auth, CRUD, etc.)", "Workorder metadata includes: name, description, scope, tasks, phases, completion_criteria, priority" ], "out_of_scope": [ "Multiple workorders per plan (deferred - keeping 1:1 relationship for focused plans)", "Nested workorders (sub-workorders within workorders)", "Multi-plan progress rollup (tracking multiple plans together)", "Team assignment features (assign workorders to team members)", "Dependency visualization (graph view of workorder dependencies)" ], "constraints": [ "Must be backward compatible - existing plans without workorder tracking continue working", "Workorder tracking enabled by default for all new plans", "If feature is too large for one plan, create multiple separate plan files instead of multiple workorders", "Workorder ID must be unique and descriptive (includes feature context)", "Must integrate seamlessly with existing 10-section planning structure" ], "technical_details": { "workorder_id_format": "WO-FEATURE-NNN (e.g., WO-AUTH-001, WO-DASHBOARD-001)", "primary_location": "Section 5: task_id_system", "cross_references": [ "Section 6: phases reference active workorder", "Section 9: checklist grouped by workorder or includes workorder tags" ], "validation_rules": [ "Format: WO-[A-Z0-9-]+-\\d{3}", "All task workorder_id references must point to defined workorder", "Each plan has exactly one workorder", "Workorder completion criteria must be defined" ] }, "questions_answered": [ { "question": "What should be included in initial implementation?", "answer": "All features: schema, validator, MCP tools, slash commands, auto-suggest, TodoWrite integration, and workorder templates" }, { "question": "How to handle existing plans?", "answer": "Backward compatible - existing plans without workorder tracking continue working unchanged" }, { "question": "Workorder ID format?", "answer": "WO-FEATURE-NNN (descriptive format with feature context, e.g., WO-AUTH-001)" }, { "question": "How many workorders per plan?", "answer": "Exactly ONE workorder per plan (1:1 relationship). If feature too large, create multiple plan files." }, { "question": "What features deferred to future?", "answer": "Multiple workorders per plan, nested workorders, multi-plan rollup, team assignment, dependency visualization" } ] }