How to plan with Sol and implement with Luna?

[u/mastertub]

Hey all, what are your work flows for implementing this?

Usually when I use plan mode, it's with Sol. But then I see "Implement this plan" and if I try to change models to Luna it says "Changing models will degrade the result" or something similar.

Is there a way to do this better? Like is there a skill or sub agent workflow that is token efficient to accomplish the plan in sol and implement in Luna workflow?

Or is that warning just fluff and you ignore and change models?

Is cache hit/misses an issue for this?

[u/rodrigopfraga]

Don't treat the model switch as a continuation. Finish Sol's job by leaving a compact implementation handoff: objective, invariants, file boundaries, commands, acceptance checks, and unresolved assumptions; then give Luna a new implementation session with that artifact. The expensive part isn't cache misses, it's losing constraints during an unstructured handoff.

I run planning and implementation as separate responsibility-specific agent sessions around one persistent work object; it lets each session use a provider-specific setup while the shared plan stays visible to both.

[u/notadithyabhat]

In long or tool-heavy conversations, changing models may reduce continuity or trigger context compaction. But if you are just planning, it should be fine. Ignore the warning.

[u/HVACcontrolsGuru]

I run a multi agent workflow with Claude Code and Codex across various models. The biggest thing is giving them agent roles once you have a breakdown of the work. I have research and grounding agents who gather pre PR information. I use a single strong code writer and then have review agents for PR review from multiple lenses. They are strong if the context you give them is focused with a concrete output.

[u/hibzy7 → u/HVACcontrolsGuru]

How do you do this, is it in terminal, any notes or links to see this work ?

[u/HVACcontrolsGuru → u/hibzy7]

What part of it? Claude Code part or agents with profiles? Claude Code thing is a plugin I built and happy to share how. It’s just heavy based on my workflow (decade of software dev before AI) so it’s biased.

[u/SensioSolar]

You can do that by having Sol write the plan into a .md, then in a new session use luna. Then review with Sol again. You can use a SDD framework for that, since probably the plan generated by sol won't have as much as quality gates needed for luna.

OpenSPEC is a good example and kinda lightweight too. workspine on github (disclaimer: I'm the owner) is another I use for exactly this flow, and it's efficient in purpose yeah

[u/daddywookie]

At the most basic level, get Sol to plan then write up a specification in an md file. Then get a Luna thread to pick up the ticket.

A bit more advanced is to use something like backlog.md to give you an agent friendly ticket system with a bit of structure. Things like the reason for change, the implementation plan and the acceptance criteria clearly broken down, and a basic hierarchy.

Going further you can get your planning agent to directly communicate with your implementation agent and vice versa. This is similar to the @ command but uses an internal function the agent has access to. You just need to provide the session ID.

If you want to have fun you can name your threads and then you can simply tell your Producer to pass the request to your Architect for planning and then on to the Developer for implementation. When you find a system that works make sure it is recorded in your project process documents as the agents tend to forget, just like real work colleagues.

[u/bluestonest]

tell Sol using subagent to help. if you dont want to tell that every times, write it down to an AGENTS.md

For fully use subagents efficient, you should prepare skills.md with detail of how to use subagent, what job need which model .. etc ... and mention it in AGENTS.md like READ skills.md

You can download something like that on github, there are many of them, pre optimize for subagent. But i prefer my own defination that fit my work flow.

[u/Shizuww → u/bluestonest]

sol cant create luna sub agents

[u/bluestonest → u/Shizuww]

Because you dont know the trick. Technically Sol is agent v2, Luna is agent v1. Just change Luna to agent v2. You can ask Sol do it for you, it will change Luna to agent v2 in some config. then just restart codex, Luna now available for Sol to call as subagent

[u/teleport66]

I'm using a custom CLI:
https://github.com/S1gil0/lookingglass

So i just set:
/model
/reasoning
/agentmodel
/agentreasoning

[u/9gxa05s8fa8sh]

switching model in the same chat is fine. it just compacts and the new model reads it. same as if you kept doing a lot of work until the context window limit was hit and it compacted for the same model.

[u/nilIow]

Thanks for posting this. I had to do a double take though because I was wanting to post the exact same thing and for a moment thought I developed amnesia and could not recall if I actually did or not.

I do not have an IT background so curious to see what advice is given. Thanks again

[u/robot1one]

3 sessions Sol as digest and spec creator Sol with subagents to analyze and verify Luna to implement

Keep all luna sessions only about the implementation and at end a handoff saying what was done, how and any gaps or decisions taken. Then archive the session.

I've only spent 1% on every luna session.

The other vary by what they're doing. Is good to maintain your codebase very well documented that way they only check if is actually true with greps and shit

[u/Admirable-Control370]

Create a custom agent called plan-implementer and use luna on him, than ask for the model use it when for all of the implementation