Feature Request: Superpowers compatibility

[materemias]

Superpowers modifies how planning is done and it seems it blocks plannonator from triggering. can you make the 2 compatible?

[ChrisEdwards]

If you turn on plan mode before using superpowers:write-plan, it will trigger plannotator. The problem is, planning mode changes how superpowers writes the plan, so its not in the normal place so you have to stop the agent after approving and tell it to write the file if you want it in the same place. The other problem is forgetting to put it into planning mode.

[arthuracn]

A related problem I am having with superpowers + plannotator is that while the plan gets kicked off in a browser tab as expected, when I click on Approve or Send Feedback, it opens a new tab with same plan/different localhost as if starting from scratch. It only goes back to claude terminal when I approve/send feedback on this second plan.
Also when I leave the initial plan idle in my browser, after a few minutes it will open this second plan on its own.

EDIT: looks like it was fixed with latest release, thanks!

NEW EDIT: issue has reappeared, same behaviour as before

[backnotprop]

PR #318 improves the OpenCode plugin's planning flow but doesn't directly address Superpowers compatibility. Superpowers uses its own write-plan tool rather than OpenCode's native plan mode, so submit_plan is never reached in that flow. Supporting Superpowers would require either hooking into its tool or having Superpowers call submit_plan explicitly. The new PLANNOTATOR_ALLOW_SUBAGENTS=1 env var may help if Superpowers runs as a subagent — it makes submit_plan visible to subagents.

[petertriho]

I'm also having issues with plannotator + superpowers on opencode. It was working fine before the #318 refactor. Not sure if this would work, but would it be possible to allow plannotator to accept any path? I'm thinking superpowers users should allow edits in plan mode for docs/superpowers/**. This way the .md are created by superpowers then any file can be passed onto submit_plan. It seems like the exploration prompt changes causes the superpowers skills to not load though.

[backnotprop]

@petertriho I updated it today to accept any path, try updating to 0.14.0 and let me know if an issue

[petertriho]

@backnotprop Thanks! Changes worked for me. Seems like it writes the plans to docs/superpowers/** then submits the raw string version to submit_plan but that works perfectly for me

[backnotprop]

YEa ended up enabling that method too, seems like dynamic/flexible is the best!

[backnotprop]

PR #378 adds a markdown file browser sidebar tab that's relevant here: #378

This enables browsing and annotating any markdown files from the project directory (or additional configured directories) directly from the plan review sidebar. The project root is auto-detected, no configuration needed. Users can also add extra directories (like docs/superpowers/) via Settings.

This came up from Superpowers users in other channels requesting the ability to browse and annotate their plan files from the filesystem. With this, Superpowers plans written to docs/superpowers/** are browsable and annotatable without leaving the review UI.

Doesn't close this issue since the broader Superpowers compatibility story (tool hooking, submit_plan integration) is separate, but it addresses the file browsing/annotation side of the workflow.