jogan/soluna-workflow — explained in plain English
Analysis updated 2026-05-18
Reduce AI reasoning costs by only escalating to expensive models when evidence shows a task is genuinely hard.
Keep an AI coding agent's context scoped to the exact files and constraints a task needs.
Track project plans in a single contract style file with explicit not started, in progress, blocked, or complete statuses.
Add a read only final review step that checks for integration problems across work done by separate AI workers.
| jogan/soluna-workflow | 16nic/comfyui-agnes-ai | 521xueweihan/hgdoll | |
|---|---|---|---|
| Stars | 19 | 19 | 19 |
| Language | — | Python | Kotlin |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | developer | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires understanding GPT-5.6 Codex's agent and effort settings before adapting the routing rules.
soluna-workflow is a configuration for GPT-5.6 Codex, a coding assistant, that sets up rules for how an AI coding agent should split work between two named roles, called Sol and Luna, to control cost while keeping code quality high. Rather than a program to install and run, this repository is a set of documentation and configuration files that tell Codex how to behave on a project. The core idea is that not every task needs the most expensive, deepest level of AI reasoning. Sol handles planning and reviewing work, while Luna handles the actual implementation. Both come in different effort levels, from a lighter setting for small mechanical edits up to a maximum setting reserved for cases where a worker gets stuck. The workflow starts most planning and coordination at a medium effort level and only escalates to a higher, more expensive level when there is concrete evidence the problem is genuinely difficult, such as conflicting requirements or a risky data migration. This escalation must be recorded rather than happening automatically just because a task looks big. The README also describes how the workflow manages the information given to the AI agents. A small file called AGENTS.md holds only rules that apply to nearly every task, such as routing policy and validation expectations. Bigger, project-specific details live in separate files under a docs and plans folder, so each worker only reads what it specifically needs rather than the whole repository and its history. Implementation tasks are handed to workers as bounded packets listing the exact files and constraints involved. A plan file acts as a contract with ordered steps, acceptance criteria, and clear status values like not started, in progress, blocked, or complete, and only the coordinating Sol role is allowed to update that shared plan file, so workers cannot create conflicting versions of the project state. A final review step, run at a high reasoning effort and restricted to read only access, checks the combined result of any tasks for integration problems across the pieces different workers touched, before the workflow considers the work finished.
A configuration for GPT-5.6 Codex that routes AI coding work between a planning and review role called Sol and an implementation role called Luna to control cost.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.