Re-Import
Re-import is a recovery and documentation refresh workflow. Most teams do not need it during normal planning or after every code change.
| 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 |
Use re-import when:
- Committed docs are materially stale, incomplete, or wrong.
- The original import missed important codebase context.
- A large change shipped outside Opheleon and the docs need a recovery draft from the current repository.
- You need to compare a regenerated draft against the last committed version before deciding what to keep.
When you re-import, Opheleon analyzes the current repository state and generates an updated draft. You can review the diff, edit anything that needs correction, and commit a new version when it is ready.
For ordinary code changes, use connected GitHub change summaries as future planning context. Reserve re-import for cases where the documentation itself needs to be regenerated from the repository.
Prior committed versions remain available in the project history.
Recent code changes
When code is pushed to a connected GitHub repository, Opheleon can summarize what changed and make that context available during future planning runs.
This helps the planning pipeline stay closer to the current state of the codebase, especially when teams ship changes outside of Opheleon.