roo parallelizability-analyzer --repo owner/repo --issues "123,124,125" Analyze specific issues within a single repository roo parallelizability-analyzer --repo RooCodeInc/Roo-Code --issues "5648,5649,5650" roo parallelizability-analyzer --urls "url1,url2,url3" Analyze issues from multiple repositories using full URLs roo parallelizability-analyzer --urls "https://github.com/owner/repo1/issues/123,https://github.com/owner/repo2/issues/456" roo parallelizability-analyzer --repo owner/repo --query "label:bug milestone:v1.0" Analyze issues matching a search query roo parallelizability-analyzer --repo RooCodeInc/Roo-Code --query "label:enhancement milestone:next-release" roo parallelizability-analyzer --input-file analysis_config.json Use a configuration file with mixed input types { "repositories": ["owner/repo1", "owner/repo2"], "issues": [123, 124, 125], "urls": ["https://github.com/owner/repo/issues/456"], "queries": [ {"repo": "owner/repo", "query": "label:bug"}, {"repo": "owner/repo", "query": "milestone:v2.0"} ] } string Repository in owner/name format conditional --repo RooCodeInc/Roo-Code comma-separated-list Issue numbers to analyze --issues "123,124,125" comma-separated-list Full GitHub issue URLs --urls "https://github.com/owner/repo/issues/123,https://github.com/owner/repo/issues/124" string GitHub search query for issues --query "label:bug milestone:v1.0 state:open" file-path JSON configuration file with analysis parameters --input-file ./analysis-config.json enum json|markdown|html|csv|yaml markdown Output format for analysis results file-path File to save analysis results --output-file ./parallelizability-report.md float 0.0-1.0 0.7 Minimum confidence level for recommendations enum conservative|balanced|aggressive balanced Risk tolerance for parallel work recommendations integer 5 Maximum number of issues per parallel group boolean true Include dependency analysis in results boolean true Include file overlap analysis boolean false Enable detailed logging and progress output boolean false Validate inputs without performing analysis { "analysis_id": "pa_20240113_142530", "timestamp": "2024-01-13T14:25:30Z", "configuration": { "risk_tolerance": "balanced", "confidence_threshold": 0.7, "max_group_size": 5 }, "issues_analyzed": [ {"repo": "RooCodeInc/Roo-Code", "number": 5648, "title": "Create parallelizability-analyzer mode"}, {"repo": "RooCodeInc/Roo-Code", "number": 5649, "title": "Improve error handling"} ], "overall_assessment": { "parallelizability_score": 0.85, "confidence_level": 0.92, "total_issues": 2, "parallel_groups": 1, "sequential_dependencies": 0 }, "parallel_groups": [ { "group_id": 1, "issues": [5648, 5649], "parallelizability_score": 0.85, "estimated_conflict_risk": "low", "coordination_requirements": ["regular sync meetings", "shared documentation"] } ], "sequential_dependencies": [], "risk_factors": [ { "type": "file_overlap", "severity": "low", "description": "Minor overlap in configuration files", "affected_issues": [5648, 5649], "mitigation": "Coordinate changes to .roomodes file" } ], "recommendations": [ "Issues 5648 and 5649 can be worked on in parallel with minimal coordination", "Establish shared documentation for configuration changes", "Plan integration testing after both issues are complete" ] } # Parallelizability Analysis Report **Analysis ID:** pa_20240113_142530 **Generated:** 2024-01-13 14:25:30 UTC **Configuration:** Balanced risk tolerance, 70% confidence threshold ## Executive Summary ✅ **High Parallelizability** (Score: 0.85, Confidence: 92%) - **2 issues analyzed** across 1 repository - **1 parallel group** identified - **0 sequential dependencies** found - **Low conflict risk** overall ## Recommended Parallel Groups ### Group 1: Core Feature Development - **Issues:** #5648, #5649 - **Parallelizability Score:** 0.85 - **Conflict Risk:** Low - **Coordination Needs:** Regular sync, shared docs ## Risk Assessment ### Low Risk Factors - **File Overlap:** Minor overlap in configuration files - **Affected Issues:** #5648, #5649 - **Mitigation:** Coordinate changes to .roomodes file ## Recommendations 1. Issues #5648 and #5649 can be worked on in parallel with minimal coordination 2. Establish shared documentation for configuration changes 3. Plan integration testing after both issues are complete ## Detailed Analysis [Additional technical details would follow...] Perform parallelizability analysis on a set of issues { "issues": [ {"repo": "owner/name", "number": 123}, {"url": "https://github.com/owner/repo/issues/456"} ], "queries": [ {"repo": "owner/name", "query": "label:bug milestone:v1.0"} ], "configuration": { "risk_tolerance": "balanced", "confidence_threshold": 0.7, "max_group_size": 5, "include_dependencies": true, "include_file_analysis": true } } Same as CLI JSON output Get the status of a running analysis { "analysis_id": "pa_20240113_142530", "status": "running|completed|failed", "progress": 0.75, "estimated_completion": "2024-01-13T14:30:00Z", "current_step": "file_overlap_analysis" } Retrieve completed analysis results json|markdown|html|csv boolean Triggered when parallelizability analysis completes { "event": "analysis_completed", "analysis_id": "pa_20240113_142530", "timestamp": "2024-01-13T14:30:00Z", "summary": { "parallelizability_score": 0.85, "parallel_groups": 1, "high_risk_conflicts": 0 }, "results_url": "/api/v1/parallelizability/results/pa_20240113_142530" } Triggered when analysis fails { "event": "analysis_failed", "analysis_id": "pa_20240113_142530", "timestamp": "2024-01-13T14:30:00Z", "error": { "code": "INSUFFICIENT_DATA", "message": "Unable to access issue data for analysis", "details": "GitHub API rate limit exceeded" } } } Create GitHub project boards based on parallelizability analysis 1. Create project board with columns for each parallel group 2. Add issues to appropriate columns 3. Set up automation rules for issue movement 4. Add labels for coordination requirements Use GitHub issue linking to track dependencies 1. Create "blocks" and "depends on" relationships 2. Add dependency labels to issues 3. Set up automated checks for dependency resolution 4. Generate dependency visualization in project board { "project_key": "PROJ", "epic_structure": [ { "epic_name": "Parallel Group 1", "issues": [ {"key": "PROJ-123", "summary": "Issue title", "priority": "High"}, {"key": "PROJ-124", "summary": "Issue title", "priority": "Medium"} ] } ], "dependencies": [ {"from": "PROJ-123", "to": "PROJ-124", "type": "blocks"} ] } { "board_name": "Parallel Work Planning", "lists": [ { "name": "Parallel Group 1", "cards": [ {"name": "Issue #123: Title", "description": "Details", "labels": ["high-priority"]}, {"name": "Issue #124: Title", "description": "Details", "labels": ["medium-priority"]} ] } ] } { "project_name": "Parallel Development", "sections": [ { "name": "Parallel Group 1", "tasks": [ {"name": "Issue #123", "notes": "Description", "assignee": "user@example.com"}, {"name": "Issue #124", "notes": "Description", "assignee": "user2@example.com"} ] } ], "dependencies": [ {"task": "Issue #123", "depends_on": ["Issue #122"]} ] } Track actual conflicts vs predicted conflicts actual_conflicts / predicted_conflicts Measure communication and coordination costs - Number of sync meetings required - Merge conflict resolution time - Code review coordination complexity Compare parallel vs sequential completion times (sequential_estimate - parallel_actual) / sequential_estimate User reports on prediction accuracy Post-completion survey or API feedback - Were conflicts predicted accurately? - Were parallel groups optimal? - What unexpected issues arose? Feedback on analysis process and recommendations Continuous feedback during work execution - Was coordination guidance helpful? - Were risk mitigation strategies effective? - How could recommendations be improved? Use feedback to improve future analyses 1. Store feedback with analysis parameters and outcomes 2. Identify patterns in prediction errors 3. Adjust algorithm weights based on historical accuracy 4. Update heuristics based on project-specific learnings 5. Improve confidence calculations using outcome data