feedback: Consider timing of --expand-all relative to task dependencies and discovered context #421

New issue

Open

opened 2025-10-14 15:53:32 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:53:32 -06:00

Owner

Originally created by @adawalli on 6/24/2025

Feedback Summary

The current --expand-all functionality expands all qualifying tasks simultaneously at the beginning of a project, potentially missing valuable context that emerges during task execution. As subtasks are completed, they often generate rich information and updates that could improve the expansion of dependent tasks. Expanding everything upfront may result in less informed or lower-quality subtasks for later dependencies.

User Context

The user is working on complex, dependency-heavy projects where tasks are interrelated. As each subtask is performed, new details, requirements, or discoveries often arise that could significantly influence how subsequent, dependent tasks should be expanded and executed.

User Impact

This limitation can lead to the generation of subtasks that lack critical context or insight, especially for tasks that depend on the outcomes of earlier ones. As a result, users may have to manually re-expand or edit tasks, reducing the efficiency and effectiveness of the automated expansion process.

Suggestions

Implement a staged expansion option that expands tasks in dependency order, allowing completed tasks to inform the expansion of their dependents.
Add a context-aware re-expansion feature, enabling users to re-expand dependent tasks after prerequisite tasks are completed and new insights are available.
Introduce an expansion timing flag (e.g., --respect-dependencies) that delays the expansion of dependent tasks until their prerequisites are finished.
Perhaps all we need is clearer documentation using existing mechanisms (e.g., it is possible to expand tasks one at a time, but it's not clear how useful that is)

Relevant Screenshots or Examples

No screenshots provided. Example scenario: In a web application project, completing authentication tasks might reveal specific security or API requirements that should influence how user management tasks are expanded.

Additional Notes

Current workaround involves manually expanding tasks as dependencies are completed, which is inefficient and undermines the purpose of the --expand-all feature. Addressing this feedback could significantly improve workflow quality and project outcomes for users managing complex task dependencies.

*Originally created by @adawalli on 6/24/2025* ### Feedback Summary The current `--expand-all` functionality expands all qualifying tasks simultaneously at the beginning of a project, potentially missing valuable context that emerges during task execution. As subtasks are completed, they often generate rich information and updates that could improve the expansion of dependent tasks. Expanding everything upfront may result in less informed or lower-quality subtasks for later dependencies. ### User Context The user is working on complex, dependency-heavy projects where tasks are interrelated. As each subtask is performed, new details, requirements, or discoveries often arise that could significantly influence how subsequent, dependent tasks should be expanded and executed. ### User Impact This limitation can lead to the generation of subtasks that lack critical context or insight, especially for tasks that depend on the outcomes of earlier ones. As a result, users may have to manually re-expand or edit tasks, reducing the efficiency and effectiveness of the automated expansion process. ### Suggestions - Implement a staged expansion option that expands tasks in dependency order, allowing completed tasks to inform the expansion of their dependents. - Add a context-aware re-expansion feature, enabling users to re-expand dependent tasks after prerequisite tasks are completed and new insights are available. - Introduce an expansion timing flag (e.g., `--respect-dependencies`) that delays the expansion of dependent tasks until their prerequisites are finished. - Perhaps all we need is clearer documentation using existing mechanisms (e.g., it is possible to expand tasks one at a time, but it's not clear how useful that is) ### Relevant Screenshots or Examples _No screenshots provided. Example scenario: In a web application project, completing authentication tasks might reveal specific security or API requirements that should influence how user management tasks are expanded._ ### Additional Notes Current workaround involves manually expanding tasks as dependencies are completed, which is inefficient and undermines the purpose of the `--expand-all` feature. Addressing this feedback could significantly improve workflow quality and project outcomes for users managing complex task dependencies.