skills.rest
jedmamosto
jedmamostoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-import

Import external plan files into GSD while detecting conflicts against PROJECT.md decisions.

Updated May 21, 2026
Search Tags:#migration#documentation automation#conflict detection#gsd#project decisions#planning validation#plan import
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-import-jedmamosto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-import
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-import-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect or conflicting planning changes by importing external GSD plan files only after checking them against existing PROJECT.md decisions.

Core Features & Use Cases

  • Conflict-detected plan import: Ingest external plan content and detect conflicts against project decisions before writing anything.
  • Deterministic GSD v1 validation: Writes the result into the GSD PLAN.md format and validates it via a checker workflow.
  • GSD-2 to GSD v1 migration: Reverse-migrates an existing GSD-2 project (using a .gsd/ directory) into GSD v1 (.planning/), optionally targeting a different path.

Quick Start

Use gsd-import to import an external plan file while detecting conflicts: give the command “Import the plan from ./.planning/new-plan.md into the current project with conflict detection.”

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 causing planning conflicts?▼

To import an external plan file safely, run the import tool with an explicit source flag like --from. The tool detects conflicts against existing PROJECT.md decisions before writing the output into the GSD PLAN.md format.

What is the process to migrate a GSD-2 project back to GSD v1 format?▼

GSD-2 to GSD v1 migration reverse-migrates an existing project using a .gsd/ directory into the .planning/ format. You run the migration tooling with the --from-gsd2 flag, optionally targeting a different output path.

How does conflict detection work when ingesting legacy project plans?▼

Conflict detection for plan ingestion validates external plan content against existing PROJECT.md decisions before writing any files. This prevents incorrect or conflicting planning changes during the adoption of third-party or legacy plans.

Do I need a specific validation step after completing a plan import?▼

Yes, you need to validate the imported plan using gsd-plan-checker. After the import tool writes the resulting GSD PLAN.md output, running the checker ensures deterministic GSD v1 validation and confirms plan integrity.

Can I target a different directory path when reverse-migrating a GSD-2 project?▼

Yes, you can target a different path when reverse-migrating a GSD-2 project. By using the --from-gsd2 source flag with the migration tooling, you can specify an output location other than the default .planning/ directory.

Related Skills

Explore More Product & Management Skills→
Poom5741Poom5741

gsd-import

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

Community
Intermediate
tinner-deinnotinner-deinno

gsd-import

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

Community
Intermediate
lgwanailgwanai
4

gsd-import

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

Community
Intermediate
SensLiaoSensLiao

gsd-import

Import external plans into GSD with conflict detection via command-line tools.

Community
Intermediate