gsd-import

Import external plan files into GSD with conflict detection against PROJECT.md.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-import-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-import
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-import-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted effort and decision drift by detecting conflicts between an external plan and your existing PROJECT.md decisions before writing anything into your GSD planning artifacts.

Core Features & Use Cases

  • External plan import with validation: Imports an external plan file, performs conflict detection against PROJECT.md decisions, and writes the result as a GSD PLAN.md, then validates it via gsd-plan-checker.
  • Reverse migration from GSD 2 to GSD v1: Converts a legacy GSD-2 project (using the .gsd/ directory) back into the GSD v1 (.planning/) format using gsd-tools.cjs from-gsd2.
  • Use Case: When collaborating across tools or timeframes, you can migrate or import plans while ensuring they don’t contradict the decisions already captured in your project.

Quick Start

Run gsd-import with the path to your external plan file to import it with conflict detection and produce an updated 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 GSD without conflicting with existing decisions?

Import external plan files by running gsd-import with the file path; it detects conflicts against existing PROJECT.md decisions before writing outputs as GSD PLAN.md. This validates the plan via gsd-plan-checker to prevent decision drift and wasted effort across collaboration timeframes.

Can I reverse-migrate a legacy GSD-2 project directory into GSD v1 planning format?

Yes, you can reverse-migrate a legacy GSD-2 project by using the gsd-tools.cjs from-gsd2 command. This converts the legacy .gsd/ directory structure back into the GSD v1 .planning/ format, with optional path overrides available based on the arguments you provide.

What is conflict detection for plan migration and when do I need it?

Conflict detection for plan migration is the process of checking an external plan against your existing PROJECT.md decisions before writing it into your GSD planning system. You need it when collaborating across tools or timeframes to ensure imported plans do not contradict established project decisions.

How do I validate imported plans using gsd-plan-checker after migration?

To validate imported plans, gsd-import automatically runs gsd-plan-checker after writing the external plan file as a GSD PLAN.md. This end-to-end import process ensures the final planning artifacts are structurally sound and do not conflict with your captured project decisions.

Does gsd-import support custom path overrides when migrating from GSD-2 to GSD v1?

Yes, gsd-import supports optional path overrides when you reverse-migrate legacy GSD-2 projects into the GSD v1 planning format. You can provide specific arguments to gsd-tools.cjs from-gsd2 to customize the source and target directories during the conversion process.