FAQ

What is Opheleon?

Opheleon is a planning system for teams building complex software. It connects business goals, product requirements, system design, implementation specs, and code-aware context so teams can move from idea to execution without losing the reasoning behind what gets built.

What documents does Opheleon create?

For new work, Opheleon drafts planning overlays: a PRD overlay (product behavior) and a Tech Approach overlay (architecture and implementation plan). Product goals get both; tech-driven goals like refactors and migrations — or goals with a concrete PRD — get only the Tech Approach overlay.

Can Opheleon start from an existing codebase?

Yes. With GitHub connected, Opheleon imports the repository to learn your existing system, then plans new work as overlays grounded in your real code. The import runs on its own; where it can’t be sure of something, it flags an unknown for you to fill in.

Does Opheleon replace product managers or engineers?

No. Opheleon drafts and organizes planning context, but humans review, correct, and approve the work.

Can Opheleon create implementation tasks?

Yes. After the Tech Approach overlay is approved, Opheleon generates tasks from its implementation plan, each with a ready-to-use prompt for a coding agent. You can optionally export them to your task management tool.

How does Opheleon keep plans current?

Re-import refreshes Opheleon’s understanding of your codebase as the code changes — you can run it yourself or have it run on a schedule. The unknowns you fill in and comments you leave persist, so each pass builds on the last.

What happens if the generated draft is wrong?

Request changes with feedback and Opheleon revises it, or reject it to have it redrafted — you guide the draft with feedback rather than editing it by hand. If Opheleon got something wrong about your existing system, fill in the relevant unknown or leave a comment, and that correction carries forward.