gsd-import

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-import-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-import
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-import-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests external planning inputs into the GSD planning system while ensuring proposed decisions do not contradict existing PROJECT.md guidance.

Core Features & Use Cases

  • Conflict detection between external plans and PROJECT.md decisions before any write.
  • Import external plan files and generate a GSD PLAN.md after successful validation.
  • Use case: a team integrates an updated external plan and confirms it does not violate current project constraints.

Quick Start

Run the import workflow to ingest a plan file and generate GSD PLAN.md with conflict checks.

Frequently Asked Questions about gsd-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is conflict detection for external plan imports and how does it work?

Yes, you can validate external planning inputs against existing project decisions before committing them. The import process requires a source file path argument, runs validation checks, and only writes the final plan document after confirming no conflicts exist.

How do I generate a plan file after validating an external planning document?

To generate a plan file after validation, run the import workflow with a source file path argument. The system performs conflict checks against project decisions and writes the finalized plan document only after the validation passes successfully.

Why does my external plan import fail before writing the project plan file?

An external plan import fails before writing when conflict detection identifies contradictions between the incoming plan and existing project decisions. The system blocks the write operation to prevent violating current project constraints until the conflicts are resolved.

What do I need to provide to run an external plan import with conflict checks?

To run an external plan import with conflict checks, you need to provide a source file path argument pointing to the external plan file. The system also requires existing project decision documents to validate against during the import process.