New Task-XX-Reports Overwriting Previous Tasks

[MadMaximusJB]

Environment (required)

Human-made!

Field	Value
Superpowers version	6.0.3
Harness (Claude Code, Cursor, etc.)	Claude Code
Harness version
Your model + version	Opus 4.8
All plugins installed
OS + shell

Is this a Superpowers issue or a platform issue?

• I confirmed this issue does not occur without Superpowers installed

What happened?

The new task reports which are now written to /.superpowers/sdd/task-xx-report are inconvenient for runs with multiple plans that each have those steps. Claude (or other agents) fail to write the file, then have to read the contents, then have to decide to overwrite it. It's a bit of a waste of tokens. Additionally, it erases evidence history of task execution.

Steps to reproduce

1. Execute several plans each with individual tasks
2. Observe the agent fail to write, read the file, then overwrite

Expected behavior

I propose that the task reports go within subfolders. Potentially named for the plan they are being executed under, or if you want simpler, just version by number.

Actual behavior

See above.

Debug log or conversation transcript

[obra]

are you running multiple concurrent plans in the same work tree?

[MadMaximusJB]

@obra I work on main sometimes as some things I just don't want in worktrees. To be fair it doesn't spin up worktrees itself anymore but I probably put something in some global file telling it not to lol. Is the intention for every single plan to be executed in it's own worktree?

[obra]

Mostly, they're not expected to run concurrently in the same worktree (including main). Something like that is always going to stomp on you. I'd be a lot more worried about the two agents getting in fights over the actual code than the planning docs. Is there a reason you don't want to let the agents use worktrees for isolation?