gsd-import

Import external plan files into GSD with conflict detection and validation.

Updated May 22, 2026

Search Tags:#planning #validation #migration #import #conflict-detection #gsd #project-decisions

Ready to run

npx skills add https://github.com/yusaduymaz/loexai --skill gsd-import-yusaduymaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-import
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-import-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you bring external plans into a GSD project without accidentally overwriting important project decisions, reducing risky manual merging and migration mistakes.

Core Features & Use Cases

Plan Import with Conflict Detection: Imports an external plan file and checks it against existing project decisions before anything is written.
GSD v2 Reverse Migration: Converts a GSD-2 project back into the GSD v1 planning structure when you need to restore an older workflow format.
Use Case: A team receives a planning document from another workspace and wants to adopt it safely while preserving local architectural choices and validation gates.

Quick Start

Ask the skill to import your external plan file and check it against the project’s decisions before saving anything.

Frequently Asked Questions about gsd-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I import external plan files into a GSD project without overwriting existing project decisions?▼

You can import external plans by running a conflict check against existing project decisions in PROJECT.md. The system generates a GSD PLAN.md output and validates it with gsd-plan-checker to ensure no local architectural choices or validation gates are overwritten during the plan handoff.

What is the best way to migrate a GSD v2 project back to the GSD v1 planning structure?▼

Reverse migration from GSD v2 repositories to the GSD v1 planning structure is supported natively. The import process converts the older workflow format by validating the incoming plan against PROJECT.md and generating a validated GSD PLAN.md file before any write completes.

How does conflict detection work when comparing an imported plan against existing project decisions?▼

Conflict detection compares the imported external plan directly against existing project decisions recorded in PROJECT.md. It intercepts risky manual merging mistakes by blocking the write operation until the generated PLAN.md output passes validation via gsd-plan-checker.

Can I use this to adopt a planning document from another workspace while preserving local validation gates?▼

Yes, you can safely adopt a planning document from another workspace while preserving local validation gates. The import process checks the external plan against your project decisions recorded in PROJECT.md, ensuring local architectural choices remain intact before generating and writing the final GSD PLAN.md file.

Do I need to run gsd-plan-checker validation manually after importing an external plan?▼

No, manual validation is not required. The import workflow automatically applies validation with gsd-plan-checker to the generated GSD PLAN.md output and requires it to pass before any write operation to the planning system is allowed to complete.