Opheleon Docs
Opheleon helps teams plan complex software work without losing the reasoning behind what gets built.
It connects business goals, product requirements, system design, implementation specs, and code-aware updates into one planning record. Start from an idea, import an existing codebase, review each layer with your team, and turn the approved plan into executable work.
Use these docs to create projects, import codebase context, review and revise generated plans, connect GitHub, turn approved plans into ready-to-use tasks for your coding agent, and keep planning aligned with what is actually shipping.
What Opheleon does
Opheleon learns your product, then plans changes to it.
It learns your system. Connect GitHub and Opheleon imports your codebase to understand the system you already have, so plans are grounded in your real code instead of memory. The import runs on its own with no setup work from your team. Where it isn't sure of something, it flags an unknown for you to fill in, and you can correct anything it got wrong with a comment — both stick, so each import gets better. Re-import refreshes that understanding as the code changes, manually or on a schedule.
It plans new work as overlays. Start from a plain-language goal and Opheleon drafts focused planning overlays on top of what it already knows about your product:
- PRD overlay — product behavior: who the change is for, what users can do, default behavior, edge cases, non-goals, and success criteria.
- Tech Approach overlay — technical direction: architecture, key technical decisions, security and failure modes, rollout, and an implementation plan that becomes tasks.
Each overlay is drafted, reviewed, and approved by your team before the next stage builds on it.
Two ways to plan a goal
- Goal → PRD → Tech Approach — when the product requirements aren’t figured out yet. Opheleon works out the product behavior first, then the technical approach, so product decisions are settled before engineering commits to an approach.
- Goal → Tech Approach — for tech-driven work like refactors, migrations, and infrastructure changes, or when you already have a concrete PRD. Opheleon goes straight to the technical approach.
Opheleon is built for the messy middle between “move fast” and “plan everything manually”: enough structure to prevent drift, without turning planning into a heavyweight process.