home/common/ai/resources/codex/gsd/skills/gsd-ingest-docs/SKILL.md
Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
npx skillsauth add kamushadenes/nix gsd-ingest-docsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<codex_skill_adapter>
$gsd-ingest-docs.$gsd-ingest-docs as {{GSD_ARGS}}.{{GSD_ARGS}} as empty.GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header → headerquestion → question"Label" — description → {label: "Label", description: "description"}id from header: lowercase, replace spaces with underscoresBatched calls:
AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]Multi-select workaround:
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.Execute mode fallback:
request_user_input is rejected or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018).--auto or --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).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_agent has no inline model parameter;
GSD embeds the resolved per-agent model directly into each agent's .toml
at install time so model_overrides from .planning/config.json and
~/.gsd/defaults.json are honored automatically by Codex's agent router.fork_context: false by default — GSD agents load their own context via <files_to_read> blocksTask(isolation="worktree") / Agent(isolation="worktree") → no direct Codex mapping.
Codex spawn_agent does 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:
spawn_agent to 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:
wait(ids) for all to completeResult parsing:
CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.close_agent(id) after collecting results from each agent
</codex_skill_adapter>--mode new, default when .planning/ is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation to gsd-roadmapper.--mode merge, default when .planning/ is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.Auto-synthesizes most conflicts using the precedence rule ADR > SPEC > PRD > DOC (overridable via manifest). Surfaces unresolved cases in .planning/INGEST-CONFLICTS.md with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.
Inputs: directory-convention discovery (docs/adr/, docs/prd/, docs/specs/, docs/rfc/, root-level {ADR,PRD,SPEC,RFC}-*.md), or an explicit --manifest <file> YAML listing {path, type, precedence?} per doc.
v1 constraints: hard cap of 50 docs per invocation; --resolve interactive is reserved for a future release.
</objective>
<execution_context> @$HOME/.codex/get-shit-done/workflows/ingest-docs.md @$HOME/.codex/get-shit-done/references/ui-brand.md @$HOME/.codex/get-shit-done/references/gate-prompts.md @$HOME/.codex/get-shit-done/references/doc-conflict-engine.md </execution_context>
<context> {{GSD_ARGS}} </context> <process> Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule. </process>data-ai
Show MemPalace status — room counts, storage usage, and palace health.
tools
Search your MemPalace — semantic search across all mined memories, projects, and conversations.
tools
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
development
Initialize a new MemPalace — guided setup for your AI memory palace with ChromaDB backend.