Codebase Import
Codebase import helps teams initialize Opheleon when they already have an existing system.
| Workflow | Use when | Output |
|---|---|---|
| Start from a goal | You are planning new work | BRD -> PRD -> HLD -> LLD |
| Import | You are adopting Opheleon for an existing codebase | Initial planning baseline from GitHub |
| Re-import | You need to recover or refresh materially stale committed docs | Recovery draft and diff against prior version |
Instead of asking your team to explain the codebase from memory, Opheleon starts from the repository itself. It analyzes the connected GitHub repo and uses that context as a grounded baseline for future planning.
Use codebase import when:
- You are adopting Opheleon for an existing product.
- Your team has existing resources that should inform future plans.
- You want a clearer baseline before planning new work.
- New team members need context on how the system works.
Import starts from implementation-level understanding and works upward into system, product, and business context. It is mainly an initialization path; the core Opheleon workflow still turns new ideas into implementation specs through the planning pipeline.
You usually do not need to re-import after normal code changes. Connected GitHub change summaries give future planning runs recent context, while re-import is reserved for recovery or refresh situations where committed docs need to be regenerated from the current repository.