skills.rest
aslaii
aslaiiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-import

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

Updated Jan 28, 2025
Search Tags:#workflow#planning#validation#import#conflict-detection#gsd#project-decisions
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-import-aslaii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-import
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-import
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-import-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest external plans into the GSD planning system while detecting conflicts against PROJECT.md decisions.

Core Features & Use Cases

  • Conflict-aware import: compare an external plan against existing PROJECT.md decisions and flag inconsistencies.
  • Write workflow: create a GSD PLAN.md after successful validation.
  • Use Case: when receiving an external plan, import it, surface conflicts, and commit a clean GSD PLAN.md for traceability.

Quick Start

Invoke the import workflow with your external plan file to detect conflicts and generate a GSD PLAN.md

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 plans into a project workflow while checking for conflicts?▼

Conflict-aware import compares an external plan file against existing project decisions to flag inconsistencies before generating a validated plan. This ensures external plans align with established project rules before being committed to the workflow.

What is the best way to merge external project plans without overriding established decisions?▼

Conflict-aware import validates external plans against existing project decisions, surfacing inconsistencies and generating a clean, traceable plan file. This approach prevents new plans from overriding established project rules during the merge.

How does conflict detection work when importing external plan files?▼

Conflict detection compares an external plan file against existing project decisions to identify inconsistencies. This validation step surfaces conflicts before the external plan is converted into a validated project plan file.

Can I generate a traceable project plan file from an external plan after validating it?▼

Yes, a conflict-aware import workflow validates an external plan against project decisions and writes a clean plan file upon successful validation. This generates a traceable project plan file ready for workflow integration.

When do I need to validate an external plan against project decisions before merging?▼

You need to validate an external plan against project decisions before merging when receiving external plans that must be integrated into project workflows. This early validation ensures conflicts are identified and maintains traceability for project decisions.

Why does my external plan import fail validation against project decisions?▼

External plan import validation fails when the imported plan contains inconsistencies that conflict with established project decisions. The conflict detection process flags these mismatches to prevent invalid plans from being written to the project workflow.

Related Skills

Explore More Software Engineering Skills→
thecomputer07thecomputer07

qsd-import

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

Community
Intermediate
coco-researchcoco-research
264

gsd-import

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

Community
Intermediate
Poom5741Poom5741

gsd-import

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

Community
Intermediate
yusaduymazyusaduymaz

gsd-import

Import external plan files into GSD with conflict detection and validation.

Community
Advanced