gsd-import

Import external project plans into GSD with automated conflict detection.

1|Updated Apr 4, 2026

Search Tags:#automation #workflow #planning #migration #conflict detection #gsd

Ready to run

npx skills add https://github.com/nnexai/git-stacks --skill gsd-import-nnexai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes references (resource) components.

What problem does it solve?

This skill solves the friction of importing external project plans into the GSD ecosystem by providing automated conflict detection against existing project decisions.

Core Features & Use Cases

Conflict Detection: Validates incoming plans against established PROJECT.md decisions to prevent architectural drift.
Reverse Migration: Safely migrates legacy GSD-2 project structures back to the standard GSD v1 format.
Use Case: When a team member provides a plan in a different format, use this skill to ingest it, verify it against current project constraints, and convert it into a standard GSD PLAN.md file.

Quick Start

Invoke the gsd-import skill by typing $gsd-import followed by the path to the external plan file you wish to ingest.

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 project plans into GSD?▼

To import external project plans into GSD, invoke the gsd-import skill with the file path to ingest the plan and convert it into a standard GSD PLAN.md file. The process validates incoming data against existing project decisions to prevent architectural drift.

What does conflict detection do when migrating plan files?▼

Conflict detection validates incoming plans against established PROJECT.md decisions to prevent architectural drift. It ensures newly imported external plans do not contradict existing project constraints before they are integrated into the GSD planning system.

Can I migrate legacy GSD-2 project directories back to GSD v1?▼

Yes, you can migrate legacy GSD-2 project directories back to the standard GSD v1 format. The gsd-import skill supports reverse migration, safely converting older project structures into the current standard format.

Do I need node.js to run gsd-tools for workflow validation?▼

Yes, you need the node.js runtime installed to execute gsd-tools.cjs for workflow execution and validation. The skill requires this environment to process automated conflict detection and ingest external plan files.

How to handle architectural drift when ingesting external plans?▼

To handle architectural drift when ingesting external plans, use the gsd-import skill to perform automated conflict detection. It checks incoming plans against established PROJECT.md decisions to verify they align with current project constraints.