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 implementation plan into executable work.

Use these docs to create projects, import codebase context, review and revise generated plans, connect GitHub, sync tasks to Linear or Trello, and keep planning aligned with what is actually shipping.

What Opheleon does

Opheleon organizes planning into four connected layers:

• BRD — Business Requirements Document: captures the business goal, problem, scope, constraints, and success criteria.
• PRD — Product Requirements Document: defines product behavior, user flows, requirements, edge cases, and acceptance criteria.
• HLD — High-Level Design: describes the system architecture, component responsibilities, data flow, and major technical decisions.
• LLD — Low-Level Design: specifies implementation details such as APIs, data models, migrations, service changes, and task-ready work.

A project can start in two ways.

For new work, start with a plain-language goal. Opheleon helps draft each planning layer in order, with review points so your team can approve, edit, or revise the plan as it develops.

For existing systems, connect GitHub and import the codebase. Opheleon uses the repository to seed planning context from what already exists, then keeps future planning aware of new code changes through automatic change summaries.

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.