feat: keep tasks.json as part of development lifecycle #90

New issue

Open

opened 2025-10-14 15:41:21 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:41:21 -06:00

Owner

Originally created by @ericdev1995 on 9/19/2025

"I want apply task-master as a tool to control development process. We can have overview which tasks already done, which tasks need to do."

We should persist the tasks.json file even when re-parsing the PRD (Product Requirements Document). This is important because:

It allows us to track the progress of completed vs. pending tasks.

In cases where the PRD is modified and re-parsed, we should not lose the status of tasks that are already done.

Instead of starting from scratch, the tool should analyze the existing codebase and update or create new tasks, while preserving the completion status of existing ones.

This approach supports an incremental and iterative development workflow, helping the team stay aligned and ensuring no work is repeated or lost during updates.

*Originally created by @ericdev1995 on 9/19/2025* > "I want apply task-master as a tool to control development process. We can have overview which tasks already done, which tasks need to do." We should persist the tasks.json file even when re-parsing the PRD (Product Requirements Document). This is important because: It allows us to track the progress of completed vs. pending tasks. In cases where the PRD is modified and re-parsed, we should not lose the status of tasks that are already done. Instead of starting from scratch, the tool should analyze the existing codebase and update or create new tasks, while preserving the completion status of existing ones. This approach supports an incremental and iterative development workflow, helping the team stay aligned and ensuring no work is repeated or lost during updates.