gsd-import
Ingests external plans and cross-references them with existing project rules to identify conflicts before implementation.
Install
mkdir -p .claude/skills/gsd-import && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18603" && unzip -o skill.zip -d .claude/skills/gsd-import && rm skill.zipInstalls to .claude/skills/gsd-import
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Ingest external plans with conflict detection against project decisions before writing anything.Key capabilities
- →Import external plan files into GSD planning system
- →Detect conflicts against existing PROJECT.md decisions
- →Validate imported plans using gsd-plan-checker
- →Reverse-migrate GSD-2 projects to GSD v1 format
How it works
The skill parses external plans and cross-references them with project constraints to identify conflicts. It supports a specific migration tool for converting legacy GSD-2 project directories to the current v1 format.
Inputs & outputs
When to use gsd-import
- →Importing external project roadmaps
- →Detecting planning conflicts
- →Validating new tasks against project scope
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-import. - Treat all user text after
$gsd-importas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected or unavailable, activate TEXT_MODE: append--textto{{GSD_ARGS}}so the workflow's built-in text-mode branching takes over. Present everyAskUserQuestioncall as a plain-text numbered list, then stop and wait for the user's reply. Do NOT pick a default and continue (#3018 / #3808). - You may only proceed without a user answer when one of these is true:
(a) the invocation included an explicit non-interactive flag (
--autoor--all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths). - Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit.spawn_agenthas no inlinemodelparameter; GSD embeds the resolved per-agent model directly into each agent's.tomlat install time somodel_overridesfrom.planning/config.jsonand~/.gsd/defaults.jsonare honored automatically by Codex's agent router.- Resolved
reasoning_effort="low|medium|high|xhigh"(xhighis a GSD/Codex tier, not a generic runtime enum) → passreasoning_efforttospawn_agentwhen the runtime/tool supports it. Omit missing, empty, inherited, or unsupported values; do not invent one-off effort literals in workflow prose. fork_context: falseby default — GSD agents load their own context via<files_to_read>blocksTask(isolation="worktree")/Agent(isolation="worktree")→ no direct Codex mapping. Codexspawn_agentdoes not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).
Spawn restriction:
- Codex restricts
spawn_agentto cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
- --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. Runsgsd-tools.cjs from-gsd2. Pass--path <dir>to migrate a project at a different path. </objective>
<execution_context> @/home/locdt/Notes/VSCode/mini-task/.codex/get-shit-done/workflows/import.md @/home/locdt/Notes/VSCode/mini-task/.codex/get-shit-done/references/ui-brand.md @/home/locdt/Notes/VSCode/mini-task/.codex/get-shit-done/references/gate-prompts.md @/home/locdt/Notes/VSCode/mini-task/.codex/get-shit-done/references/doc-conflict-engine.md </execution_context>
<context> {{GSD_ARGS}} </context> <process> If `--from-gsd2` is in {{GSD_ARGS}}: Run: `node "$HOME/.codex/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>
Prerequisites
Limitations
- →Does not write workflow artifacts until user input is provided or auto-flags are set
- →Requires manual worktree protocol for workflows needing worktree isolation
How it compares
Unlike manual planning, this skill automates conflict detection against existing project decisions before any files are written.
Compared to similar skills
gsd-import side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-import (this skill) | 0 | 1mo | No flags | Intermediate |
| planning-with-files | 233 | 6mo | Review | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| pmbok-project-management | 38 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by haketienloc10
View all by haketienloc10 →You might also like
planning-with-files
davila7
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
clickup
civitai
Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.
ma-playbook
alirezarezvani
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.