gsd-import

To import external project plans and check for conflicts, you ingest the plan file from a specified path, detect conflicts against PROJECT.md decisions, and write the resolved output as a GSD PLAN.md. This prevents unapproved changes from entering your workflow.

The best way to convert external planning artifacts into a GSD format is to import the file and validate it against PROJECT.md decisions. This enforces alignment with existing project rules before generating the final GSD PLAN.md output.

Conflict detection works by comparing the ingested external plan file against existing PROJECT.md decisions. It surfaces any conflicting changes for review, ensuring that the final GSD PLAN.md only contains approved and consistent project decisions.

Yes, you can validate a generated GSD PLAN.md to ensure consistency by using gsd-plan-checker. After importing an external plan and resolving conflicts, the checker validates the resulting plan file for correctness within the GSD planning system.

If your imported plan has conflicts against PROJECT.md decisions, you must review and address the surfaced conflicts before proceeding. Once conflicts are resolved and approved, you can safely write the finalized plan as your GSD PLAN.md.

Yes, you need a specific file path to start importing external plans into the GSD system. You provide the source location using the --from flag, which triggers the ingestion, conflict detection, and PLAN.md generation workflow.