gsd-import

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

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-import-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-import
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-import-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents inconsistent planning by detecting conflicts between externally provided GSD plans and existing PROJECT.md decisions before any files are written.

Core Features & Use Cases

  • Conflict-aware ingestion: Imports an external plan while checking it against current project decisions to avoid overwriting assumptions.
  • Validated output generation: Writes the resulting GSD PLAN.md and validates it via gsd-plan-checker.
  • GSD version migration: Reverse-migrates a GSD-2 project (.gsd/) back into the GSD v1 (.planning/) format for restoration or tooling compatibility.
  • Typical use case: You receive a plan from another workspace or branch and need to reconcile it with your current decisions without silently introducing contradictions.

Quick Start

Run the gsd-import skill to import an external plan file by specifying its path with --from.

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 without overwriting existing decisions?

You can import external plans safely by using conflict detection against PROJECT.md decisions before writing updates. This prevents inconsistent planning by validating assumptions and checking for contradictions before any files are written.

What is GSD version migration and when do I need reverse migration?

GSD version migration restores a GSD-2 project (.gsd/) back into the GSD v1 (.planning/) format. You need this reverse migration for restoration or tooling compatibility when reconciling plans across different GSD workspace versions.

How to validate an imported plan file against current project decisions?

To validate an imported plan file, run the import workflow to write the GSD PLAN.md and then validate it with gsd-plan-checker. This ensures the reconciled plan aligns with your current project decisions.

Can I ingest a plan from another workspace branch into my current project?

Yes, you can ingest a plan from another workspace or branch by specifying its file path with the --from command. The system reconciles it with your current decisions to avoid silently introducing contradictions.

Do I need gsd-tools to run the plan import workflow?

You need either gsd-tools.cjs using the from-gsd2 command or the full import workflow that writes GSD PLAN.md. Both methods require validating the output with gsd-plan-checker to ensure safe migration.