Proposal: The apply proposal should instruct the agent to delegate tasks to subagents

[antonio-ivanovski]

While working on any proposal size my workflow is to have the best model at disposal as the main model (great results with Opus 4.5) and some cheaper as the worker model (all will work, Sonnet 4.5 is excellent). I have stable results with simple addition to the apply command

And the best part, the complete flow took 30% of the context, leaving much room for further debugging and changes.

To achieve this, i have one simple change the apply command:

**Steps**
Track these steps as TODOs and complete them one by one.
1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
+2. Work through tasks sequentially (individually or in small batches) ONLY by delegating to @general subagent (never by yourself), keeping edits minimal and focused on the requested change.
3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
5. Reference `openspec list` or `openspec show <item>` when additional context is required.

This proposal is also in line with the latest workflow claude-code is making with tasks and delegating to subagents.

Maybe this can be added to the source too?

[TabishB]

@antonio-ivanovski The issue is we're a cross-platform tool and this is a platform specific instruction. We are thinking about looking into doing a Claude Code specific integration. Which should now be possible since we have made the internals of OpenSpec a lot more hackable.

But this is a really good data point, thank you!

[antonio-ivanovski]

@TabishB I am using opencode and it is working. Not sure about others.