external-plan-import

To import a PRD or external roadmap, provide the document or link to the system. It parses goals, tasks, and dependencies, then checks for conflicts with existing decisions before committing the validated items into the ROADMAP.

When an imported plan conflicts with existing architecture or dependencies, the system detects these issues during pre-import checks. It then presents resolution options and employs safe-merge behavior before updating the roadmap.

Yes, you can safely import external design documents without overwriting current constraints. The system performs conflict detection against existing phases and constraints, preserving the original source for reference while only committing non-conflicting items.

External plan parsing extracts goals, tasks, dependencies, and acceptance criteria from the source document. It translates these validated components into distinct ROADMAP phases while emitting an import-complete signal upon success.

You do not need to manually find naming conflicts when importing specs. The system automatically detects conflicts including naming and architecture, presenting you with resolution options to choose from before the commit phase.

The best way to safely integrate external specs is using a conflict-aware import process. This approach validates the external plan against internal decisions, offers resolution options for conflicts, and translates the clean data into ROADMAP phases.