plan-split

To split research documents into dependency-ordered implementation plans, you supply the research file path to the workflow. It analyzes the document to extract tasks, groups them by dependencies, and enforces a maximum complexity of 5 points per plan.

The maximum complexity limit for a generated implementation plan is 5 points. The tool groups tasks into bounded plans that preserve prerequisites order, ensuring no single plan exceeds this complexity threshold during the split.

Yes, you can automatically create GitHub issues from an implementation plan. The workflow generates a GitHub issue for each plan it creates from the research document and tracks progress automatically without manual entry.

Re-running the plan generation workflow does not create duplicate GitHub issues. It supports idempotent re-running by detecting existing plan files and existing GitHub issues, avoiding duplicates on subsequent executions.

You do not need to manually define task dependencies before splitting a research document. The workflow analyzes the research document to automatically extract tasks and dependencies, grouping them into implementation plans while preserving prerequisites order.

The best way to manage bounded complexity when planning software engineering tasks is using a workflow that splits research into plans with a maximum complexity of 5 points. This enforces bounded complexity per plan while preserving the dependency order of prerequisites.