Choosing a Workflow

Opheleon’s primary workflow starts from an idea or business goal and turns it into implementation-ready work. Import is available when you need to initialize Opheleon with existing resources first.

Start from a goal

Use this when you have an idea, product initiative, or technical change that needs to become executable work.

You provide a plain-language goal, and Opheleon breaks the problem down layer by layer:

1. BRD
2. PRD
3. HLD
4. LLD

This is the core Opheleon path: business goal to product shape, product shape to system design, and system design to implementation specs.

Import an existing codebase

Use this when your team already has existing resources and Opheleon needs that context before future planning begins.

You connect a GitHub repository, choose the project, and Opheleon analyzes the codebase to initialize planning context from the implementation upward.

This is best when you are adopting Opheleon for an existing product and need a grounded baseline before planning new work.

Re-import

Re-import is a recovery path, not a normal requirement after most code changes.

Use it when committed documents are materially stale, incomplete, or wrong and you need Opheleon to regenerate a draft from the current repository state.

For ordinary ongoing work, rely on GitHub change summaries as planning context during future runs instead of re-importing the project.