Automated summary
Ingests a repo's existing ADRs, PRDs, SPECs and docs to build a complete .planning/ setup, or to merge them into an existing one while blocking on unresolved contradictions.
Strengths
- One-pass synthesis of multiple document types into PROJECT.md, REQUIREMENTS.md, ROADMAP.md and STATE.md, with final generation delegated to gsd-roadmapper.
- Deterministic precedence rule ADR > SPEC > PRD > DOC (overridable via manifest) plus a conflict report split into auto-resolved, competing-variants and unresolved-blockers buckets.
- BLOCKER gate from the shared conflict engine: no destination file is written while an unresolved contradiction exists.
- Auto-discovery of conventional locations (docs/adr, docs/prd, docs/specs, docs/rfc, root-level files) or an explicit YAML manifest, with both new and merge modes.
Limitations
- Hard cap of 50 documents per invocation.
- --resolve interactive is advertised but reserved for a future release; only automatic resolution is actually available.
- Relies on the gsd-core workflows and references under ~/.claude, and on the gsd-roadmapper skill for final generation.
Use it when a repo already holds ADRs, PRDs or SPECs and you want a .planning/ created or extended without re-authoring those documents by hand.
Avoid it when there are no pre-existing planning documents, when the corpus exceeds 50 docs, or when contradictions require interactive human arbitration that is not yet supported.
Security analysis
SafeThe skill instructs an agent to read existing planning documents, synthesize them, and write planning files. It declares Bash and Agent as allowed tools, but no destructive, exfiltrating, or obfuscated commands are present. The workflow includes a BLOCKER gate that prevents writes when unresolved contradictions exist, which is a safety measure. The use of Bash is limited to legitimate file discovery and document processing.
No concerns found
How this analysis is madeExamples
Ingest everything in docs/adr/ and docs/prd/ and bootstrap a .planning/ setup from it — show me the conflict report before writing any files.Merge the new SPEC files in docs/specs/ into our existing .planning/, and hard-block if anything contradicts a locked decision.Use the manifest ingest-manifest.yaml to ingest these docs into .planning/ in merge mode, with SPECs taking precedence over PRDs where they disagree.name: gsd-ingest-docs description: "Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo." argument-hint: "[path] [--mode new|merge] [--manifest <file>] [--resolve auto|interactive]" allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- AskUserQuestion
- Agent
<objective> Build the full `.planning/` setup (or merge into an existing one) from multiple pre-existing planning documents — ADRs, PRDs, SPECs, DOCs — in one pass.
- Net-new bootstrap (
--mode new, default when.planning/is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation togsd-roadmapper. - Merge into existing (
--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/.claude/gsd-core/workflows/ingest-docs.md @$HOME/.claude/gsd-core/references/ui-brand.md @$HOME/.claude/gsd-core/references/gate-prompts.md @$HOME/.claude/gsd-core/references/doc-conflict-engine.md </execution_context>
<context> $ARGUMENTS </context> <process> Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule. </process>From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ingest-docs-for-planning-setup-mrwakbf2/download' --output '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md.part' && mv '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md.part' '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md' && test -s '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gsd-ingest-docs' && cp -R '.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2' '.claude/skills/gsd-ingest-docs'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ingest-docs-for-planning-setup-mrwakbf2'openskills read 'ingest-docs-for-planning-setup-mrwakbf2'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ingest-docs-for-planning-setup-mrwakbf2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.