gsd-import

Imports external plan files into GSD while detecting conflicts with PROJECT.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-import-beibei-clic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-import
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-import-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The GSD import skill prevents planning chaos by importing external plan files into your GSD project while detecting conflicts against existing PROJECT decisions before anything is written.

Core Features & Use Cases

  • Plan ingestion with conflict detection: Imports an external plan file into the GSD planning flow, validates the result via the gsd-plan-checker, and detects conflicts against PROJECT.md decisions.
  • GSD v2 to v1 reverse migration: Migrates a GSD-2 project (.gsd directory) back to the GSD v1 (.planning) format using gsd-tools, optionally targeting a different path.
  • Use Case: You have a plan created elsewhere (or an older GSD-2 project) and you want it to integrate with your current project without accidentally contradicting your established decisions.

Quick Start

Run gsd-import with --from path/to/plan.md to ingest the plan with conflict detection against your PROJECT.md decisions.

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 GSD workflows without causing conflicts?

To import external plan files into GSD workflows safely, use the gsd-import tool with the --from flag to ingest the plan and automatically detect conflicts against existing PROJECT.md decisions before writing.

What is the best way to migrate a GSD v2 project back to the v1 format?

Migrating a GSD v2 project back to v1 involves using gsd-tools/cjs to reverse-migrate the .gsd directory into the .planning format, optionally specifying a different target path during the process.

How does conflict detection work when onboarding new plans into a GSD project?

Conflict detection during GSD plan onboarding validates the imported plan through the gsd-plan-checker and cross-references it against established PROJECT.md decisions to prevent planning chaos before any files are written.

Can I integrate externally authored workflows into my current GSD planning system?

Yes, you can integrate externally authored workflows by running gsd-import with the --from or --from-gsd2 input handling, which performs end-to-end validation before writing to ensure seamless integration.

Do I need specific tools to validate migrated GSD project structures?

Validating migrated GSD project structures requires gsd-tools/cjs for the migration process and gsd-plan-checker to perform end-to-end validation before the final plan is written.