starred/planning-with-files

Fork 0

mirror of https://github.com/OthmanAdi/planning-with-files.git synced 2026-04-25 16:06:02 +03:00

[GH-ISSUE #50] How to handle multiple long-running tasks? #31

New issue

Open

opened 2026-03-03 18:50:09 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 18:50:09 +03:00

Owner

Originally created by @hzura on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/50

Great project! I'm wondering how to handle scenarios where multiple tasks are in progress simultaneously - for example, when one task is blocked waiting for external dependencies (PR review, API access, etc.) and I need to work on another task in the meantime.

Is there a recommended pattern for this?

Originally created by @hzura on GitHub (Jan 22, 2026). Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/50 Great project! I'm wondering how to handle scenarios where multiple tasks are in progress simultaneously - for example, when one task is blocked waiting for external dependencies (PR review, API access, etc.) and I need to work on another task in the meantime. Is there a recommended pattern for this?

kerem commented

2026-03-03 18:50:10 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 22, 2026):

Recommended Pattern for Multiple Long-Running Tasks

Great question! Here's the pattern I recommend:

Option 1: Task-Specific Directories (Recommended)

project/
├── .planning/
│   ├── feature-auth/
│   │   ├── task_plan.md
│   │   ├── findings.md
│   │   └── progress.md
│   ├── bugfix-login/
│   │   ├── task_plan.md
│   │   ├── findings.md
│   │   └── progress.md
│   └── refactor-api/
│       └── ...

Usage:

"I need to switch to the auth feature task"
→ Claude reads .planning/feature-auth/task_plan.md
→ Picks up where you left off

Option 2: Named Files (Simpler)

project/
├── task_plan_feature-auth.md
├── task_plan_bugfix-login.md
├── findings_feature-auth.md
└── ...

Context Switching Protocol

When switching between tasks:

Pause current task:
- Update task_plan.md with current status
- Note in progress.md: "Paused - waiting for PR review"
Resume blocked task:
- Tell Claude: "Resume the auth feature task"
- Claude reads the task's planning files
- Continues from last checkpoint

Example Workflow

Time	Action	Files Used
Day 1	Start auth feature	`.planning/feature-auth/*`
Day 2	Blocked on PR review, switch to bugfix	`.planning/bugfix-login/*`
Day 3	PR approved, resume auth	`.planning/feature-auth/*`

Key Principle

The filesystem is your memory. Each task gets its own "memory space" so context is never lost.

This is exactly how Manus handles long-running tasks - they treat the filesystem as external memory that persists across sessions.

Hope this helps! Let me know if you need more details.

@OthmanAdi commented on GitHub (Jan 22, 2026): ## Recommended Pattern for Multiple Long-Running Tasks Great question! Here's the pattern I recommend: ### Option 1: Task-Specific Directories (Recommended) ``` project/ ├── .planning/ │ ├── feature-auth/ │ │ ├── task_plan.md │ │ ├── findings.md │ │ └── progress.md │ ├── bugfix-login/ │ │ ├── task_plan.md │ │ ├── findings.md │ │ └── progress.md │ └── refactor-api/ │ └── ... ``` **Usage:** ``` "I need to switch to the auth feature task" → Claude reads .planning/feature-auth/task_plan.md → Picks up where you left off ``` ### Option 2: Named Files (Simpler) ``` project/ ├── task_plan_feature-auth.md ├── task_plan_bugfix-login.md ├── findings_feature-auth.md └── ... ``` ### Context Switching Protocol When switching between tasks: 1. **Pause current task:** - Update `task_plan.md` with current status - Note in progress.md: "Paused - waiting for PR review" 2. **Resume blocked task:** - Tell Claude: "Resume the auth feature task" - Claude reads the task's planning files - Continues from last checkpoint ### Example Workflow | Time | Action | Files Used | |------|--------|------------| | Day 1 | Start auth feature | `.planning/feature-auth/*` | | Day 2 | Blocked on PR review, switch to bugfix | `.planning/bugfix-login/*` | | Day 3 | PR approved, resume auth | `.planning/feature-auth/*` | ### Key Principle The filesystem is your memory. Each task gets its own "memory space" so context is never lost. This is exactly how Manus handles long-running tasks - they treat the filesystem as external memory that persists across sessions. Hope this helps! Let me know if you need more details.

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/planning-with-files#31

No description provided.

Rows
Columns