agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-import/SKILL.md

gsd-import

Skill1 starsChanged 31 days agoMITView on GitHub

Ingest external plans with conflict detection against project decisions before writing anything.

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 3 are common, 0 are distinctive, and 1 is very specific to this project.

  • 3

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 19
  2. Common:

    --from: Import an external plan file, detect conflicts, write as GSD PLAN.md, validate via gsd-plan-checker.

    line 21
  3. Very specific:

    If --from-gsd2 is in $ARGUMENTS: Run: node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2 Pass --path <dir> if provided.

    line 37
  4. Common:

    Stop here (do not run the standard import workflow).

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<objective> Import external plan files into the GSD planning system with conflict detection against PROJECT.md decisions.
  • --from: Import an external plan file, detect conflicts, write as GSD PLAN.md, validate via gsd-plan-checker.
  • --from-gsd2: Reverse-migrate a GSD-2 project (.gsd/ directory) back to GSD v1 (.planning/) format. Runs gsd-tools.cjs from-gsd2. Pass --path <dir> to migrate a project at a different path.</objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/import.md @$HOME/.claude/get-shit-done/references/ui-brand.md @$HOME/.claude/get-shit-done/references/gate-prompts.md @$HOME/.claude/get-shit-done/references/doc-conflict-engine.md </execution_context>

<context> $ARGUMENTS </context><process> If `--from-gsd2` is in $ARGUMENTS: Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2` Pass `--path <dir>` if provided. Present the migration result to the user. Stop here (do not run the standard import workflow).

Otherwise, execute the import workflow end-to-end. </process>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free