gsd-import

Import external plan files into GSD PLAN.md with conflict detection.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-import-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-import
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-import-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents accidental overwrites and misalignment by importing external plan files into the GSD planning system while detecting conflicts against the project’s existing decisions.

Core Features & Use Cases

  • Plan ingestion with conflict detection: Imports an external plan file into a GSD PLAN.md workflow only after checking for conflicts with PROJECT.md decisions.
  • GSD v2 to GSD v1 migration: Reverse-migrates a GSD-2 project (a .gsd/ directory) back to the GSD v1 (.planning/) format to restore compatibility and reuse prior tooling.
  • Validation-first execution: Runs the import end-to-end and validates the output via gsd-plan-checker, reducing the risk of producing an invalid planning artifact.

Quick Start

Run the gsd-import skill with --from <filepath> to import an external plan file, detect conflicts against PROJECT.md, and write the resulting GSD PLAN.md.

Frequently Asked Questions about gsd-import

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

FAQPage Schema
How do I import an external plan file into a GSD workflow without overwriting existing project decisions?

The tool ensures safe plan ingestion by checking for conflicts against existing PROJECT.md decisions before writing the final GSD PLAN.md, preventing accidental overwrites and misalignment.

Can I migrate a GSD-2 project back to GSD v1 format?

Yes, you can reverse-migrate a GSD-2 project to GSD v1 format. Use the --from-gsd2 and --path flags to convert a .gsd directory back to the .planning format, restoring compatibility with prior tooling.

How does plan migration handle conflict detection against existing project decisions?

Conflict detection works by comparing incoming external plan artifacts against existing decisions in PROJECT.md, ensuring the imported plan does not misalign with established project rules before writing the output.

What validation runs after importing an external plan file?

After importing an external plan file, validation-first execution runs the gsd-plan-checker to validate the generated GSD PLAN.md output end-to-end, reducing the risk of producing an invalid planning artifact.

When do I need to use the --from-gsd2 flag for plan consolidation?

You need the --from-gsd2 flag when converting a GSD-2 project directory back to GSD v1. This applies to migration scenarios where you must restore compatibility and reuse prior planning tooling.

What are the limitations of importing external plan artifacts with conflict detection?

The limitation is that imports require an existing PROJECT.md to check against. Without it, conflict detection cannot ensure correctness, and the gsd-plan-checker validation may fail to produce a valid planning artifact.