skills.rest
mcampbellr
mcampbellrCOMMUNITY
Explore all skills by this author →
Website𝕏@mariocampbellrGitHub

gsd-ingest-docs

Bootstrap or merge .planning/ setups from ADRs, PRDs, SPECs, and DOCs.

Updated Apr 22, 2025
Search Tags:#planning#PRD#merge#ADR#conflict resolution#bootstrap
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-ingest-docs-mcampbellr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-ingest-docs
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-ingest-docs-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation or merging of .planning/ setups by integrating existing ADRs, PRDs, SPECs, and documents, reducing manual efforts and ensuring consistency.

Core Features & Use Cases

  • Automatic Setup Bootstrap: Create complete .planning/ files from synthesized document content, utilizing gsd-roadmapper for final generation.
  • Merge into Existing Setup: Append phases and requirements from ingested documents, with built-in contradiction resolution.
  • Precedence-Based Resolution: Synthesizes conflicts using the precedence rule ADR > SPEC > PRD > DOC, with unresolved cases logged in .planning/INGEST-CONFLICTS.md.

Quick Start

To bootstrap a new .planning/ setup, use the gsd-ingest-docs skill with the following command: gsd-ingest-docs [path] --mode new.

Frequently Asked Questions about gsd-ingest-docs

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

FAQPage Schema
How do I bootstrap a .planning/ setup from existing PRDs, ADRs, and SPECs?▼

To bootstrap a .planning/ setup from existing PRDs, ADRs, and SPECs, use the ingest command in new mode. It synthesizes document content to generate complete planning files automatically.

How does conflict resolution work when merging multiple planning documents?▼

Conflict resolution when merging planning documents follows the precedence rule ADR > SPEC > PRD > DOC. Unresolved contradictions are logged in the INGEST-CONFLICTS.md file.

Can I merge new requirements into an existing .planning/ directory?▼

Yes, you can merge new requirements into an existing .planning/ directory. The process appends phases and requirements from ingested documents while resolving contradictions using precedence rules.

What happens to unresolved conflicts during a planning document merge?▼

Unresolved conflicts during a planning document merge are logged into the .planning/INGEST-CONFLICTS.md file. This provides interactive resolution for cases that deterministic precedence rules cannot handle.

What document types are supported for ingesting into a .planning/ setup?▼

Supported document types for ingesting into a .planning/ setup include ADRs, PRDs, SPECs, and general DOCs. The tool requires access to these specific documents to execute.

Related Skills

Explore More Software Engineering Skills→
darsoohoodarsoohoo

recipe-update-doc

Update design documents with review and consistency verification.

Community
Advanced
cshyangcshyang

gsd:roadmap

Generate a phased roadmap with phases and waves in ROADMAP.md.

Community
Intermediate
nnexainnexai
1

gsd-ingest-docs

Synthesize ADRs, PRDs, and specifications into a standardized .planning/ directory.

Community
Advanced
roycolumbia-coderoycolumbia-code

gsd-ingest-docs

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

Community
Intermediate