gsd-import

To ingest external plans into a GSD planning system, run the import workflow with --from <filepath> to read the external file and write or update a GSD PLAN.md. The ingestion process automatically checks for conflicts against existing PROJECT.md decisions before committing.

Conflict detection for external plan ingestion is the process of validating imported plans against existing PROJECT.md decisions. It ensures that newly ingested plan files remain consistent and non-conflicting with established project decisions before any data is written.

You import an external plan file without breaking project decisions by using a tool that performs automated conflict detection. The system validates the incoming plan against PROJECT.md decisions to ensure consistency and prevents writing conflicting updates.

Yes, you can validate plan integrity across multiple projects before committing. The ingestion workflow applies validation via gsd-plan-checker to verify consistency and ensure imported plans do not conflict with existing project decisions.

The best way to automate external plan ingestion and conflict checks is to run a workflow that accepts --from <filepath>, performs conflict detection against PROJECT.md, writes a GSD PLAN.md, and validates the result using gsd-plan-checker.