Document Types
When you plan new work, Opheleon drafts overlays — focused planning documents grounded in your existing system. A goal-based project produces one or two.
PRD overlay — Product Requirements
The PRD overlay defines what the product should do.
It usually includes:
- Target users and actors
- User-facing behavior and flows
- Functional requirements and acceptance criteria
- Edge cases
- Non-goals
- Success criteria
Answers: “What should users be able to do, and how should the product behave?”
Workspace admins can invite members, assign roles, change access, and see a clear confirmation before permissions take effect.
Do not include: architecture decisions, schemas, migrations, or low-level API behavior — those belong in the Tech Approach overlay.
Tech Approach overlay — Technical direction and implementation plan
The Tech Approach overlay defines how to build what the PRD overlay describes.
It usually includes:
- Architecture direction and key technical decisions
- Data ownership and important contracts
- Security and failure-mode decisions
- Migration, backfill, and rollout posture
- A project plan that becomes implementation tasks
Answers: “How should we build this, and what work does it break down into?”
Permissions are evaluated through a centralized authorization layer. Add role assignment persistence, enforce checks on member-management endpoints, migrate existing admins, and ship behind a rollout flag.
Do not include: unresolved product decisions that should be settled in the PRD overlay first.
When both overlays are produced, the PRD overlay is completed and approved before the Tech Approach overlay, so product scope is settled before engineering commits to an approach. For tech-driven work — refactors, migrations, or goals that already have a concrete PRD — Opheleon produces only the Tech Approach overlay.