skills.rest
ThiagoVitale
ThiagoVitaleCOMMUNITY
Explore all skills by this author →
GitHub

gsd-ingest-docs

Create or merge a .planning/ directory from ADRs, PRDs, SPECs, and other documents with precedence-based conflict resolution.

Updated May 3, 2026
Search Tags:#planning#PRD#document automation#ADR#repository management#SPEC
One-click install
npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-ingest-docs-thiagovitale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-ingest-docs
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-ingest-docs-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation or merging of a .planning/ directory from existing ADRs, PRDs, SPECs, and other documents within a repository, streamlining the planning process.

Core Features & Use Cases

  • Bootstrap or Merge Planning: Automatically generate or merge a .planning/ directory from various document types.
  • Precedence Rule: Automatically resolves conflicts using the precedence rule ADR > SPEC > PRD > DOC.
  • Conflict Reporting: Identifies and reports unresolved conflicts in .planning/INGEST-CONFLICTS.md.

Quick Start

To bootstrap a new planning setup, run $gsd-ingest-docs --mode new. To merge into an existing setup, run $gsd-ingest-docs.

Frequently Asked Questions about gsd-ingest-docs

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

FAQPage Schema
How do I automate planning setup from existing ADRs and PRDs in a repository?▼

Automating planning setup involves generating or merging a .planning/ directory from existing ADRs, PRDs, and SPECs. Run the ingest command in new mode to bootstrap a setup, or default mode to merge into an existing directory.

How are document conflicts resolved when merging PRDs and SPECs?▼

Document conflicts are resolved using the precedence rule ADR > SPEC > PRD > DOC. Unresolved conflicts are automatically identified and reported in a dedicated .planning/INGEST-CONFLICTS.md file.

What is the best way to bootstrap a new .planning directory from multiple document types?▼

Bootstrapping a new .planning directory requires running the ingest tool in new mode. This automatically processes multiple document types, applying precedence rules to establish the initial planning structure.

Do I need a manifest file to ingest repository documents into a planning directory?▼

A manifest file is not strictly required if directory convention discovery is possible. The tool requires either explicit directory convention discovery or an explicit manifest file to process documents.

Can I merge new ADRs into an existing .planning setup without overwriting current files?▼

Merging new ADRs into an existing .planning setup uses the default ingest mode. This process intelligently merges documents, applying the ADR > SPEC > PRD > DOC precedence rule to handle any overlapping content.

Why does document ingestion report unresolved conflicts in INGEST-CONFLICTS.md?▼

Unresolved conflicts are reported in INGEST-CONFLICTS.md because the automatic precedence rule cannot resolve specific overlapping content. This file identifies exactly where manual review is needed within the .planning directory.

Related Skills

Explore More Product & Management Skills→
nobu007nobu007

spec-flow-auto

Automate PRD-to-SPEC workflows generating requirements.md, design.md, and tasks.md.

Community
Advanced
aslaiiaslaii

gsd-ingest-docs

Ingest ADR, PRD, SPEC, and DOC files into .planning/ workflows.

Community
Advanced
antgroupantgroup
16

file-organizer-skill

Organize local files into categorized directories by extension or timestamp.

Official
Intermediate
deerawandeerawan
1

gsd-ingest-docs

Ingest ADR, PRD, SPEC, and DOC files into a repo's .planning/ system.

Community
Advanced