gsd-ingest-docs

Merge planning documents into an existing `.planning/` setup.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-ingest-docs-roycolumbia-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/roycolumbia-code/claude-global-config/tree/main/skills/_audit-disabled-20260706-1136/gsd-ingest-docs
Command: npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-ingest-docs-roycolumbia-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of synthesizing or merging planning documents (ADRs, PRDs, SPECs, DOCs) into a comprehensive .planning/ setup, reducing manual effort and potential inconsistencies.

Core Features & Use Cases

  • Document Synthesis: Builds a full .planning/ setup from synthesized content derived from multiple documents.
  • Merge Mode: Merges additional planning documents into an existing .planning/ setup, resolving contradictions and appending new content.
  • Use Case: Ideal for teams that want to quickly generate a planning document setup or integrate additional documents into their existing structure.

Quick Start

Activate the gsd-ingest-docs skill with the command 'merge planning documents into existing setup' and specify the path to your documents.

Frequently Asked Questions about gsd-ingest-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge planning documents like PRDs and ADRs into an existing setup?

To merge planning documents, activate the skill and specify your document paths. It integrates ADRs, PRDs, SPECs, and DOCs into an existing `.planning/` setup, resolving contradictions and appending new content automatically.

What is the best way to automate planning document synthesis for a new project?

Automating planning document synthesis builds a full `.planning/` setup from multiple documents in one pass. It derives coherent content from your specified ADRs, PRDs, SPECs, and DOCs to reduce manual effort.

Do I need a manifest file to synthesize planning documents?

Yes, planning document synthesis requires a manifest file. The manifest specifies document paths and precedence, allowing the process to automatically merge content and interactively resolve any conflicts.

How does conflict resolution work when merging multiple planning documents?

Conflict resolution during document merging uses the precedence defined in your manifest file. For overlapping contradictions, it offers interactive options to ensure the final `.planning/` setup remains coherent.

Can I integrate SPECs and DOCs into an existing `.planning/` directory structure?

Yes, you can integrate SPECs and DOCs into an existing `.planning/` directory. The merge mode handles these document types, resolving contradictions and appending new content to maintain structure.