gsd-ingest-docs

Ingest ADRs, PRDs, SPECs, and RFCs to synthesize .planning/ outputs.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-ingest-docs-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-ingest-docs
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-ingest-docs-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the manual, error-prone work of creating and keeping a repo’s .planning/ structure aligned with your existing ADRs, PRDs, SPECs, and other documentation.

Core Features & Use Cases

  • Net-new bootstrap: Synthesizes PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md from ingested planning documents when .planning/ is absent.
  • Merge into existing planning: Appends phases and requirements from new ingested docs while hard-blocking contradictions with locked decisions.
  • Conflict-aware ingestion: Auto-synthesizes most conflicts using precedence ADR > SPEC > PRD > DOC, writes .planning/INGEST-CONFLICTS.md for unresolved cases, and enforces the BLOCKER safety gate to prevent writing when unresolved blockers exist.
  • Flexible inputs: Discovers documents by directory convention (e.g., docs/adr, docs/prd, docs/specs, docs/rfc, and root-level {ADR,PRD,SPEC,RFC}-*.md) or uses an explicit --manifest to control {path, type, precedence?}.

Quick Start

Run gsd-ingest-docs on your repository to generate a fresh .planning/ suite from existing ADR, PRD, SPEC, and DOC files.

Frequently Asked Questions about gsd-ingest-docs

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

FAQPage Schema
How do I generate a project roadmap and requirements from existing ADRs and PRDs?

You can bootstrap a complete .planning/ structure by ingesting ADRs, PRDs, SPECs, and RFCs. The tool synthesizes PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md directly from your existing planning documents.

How does conflict resolution work when ingesting PRDs and SPECs with contradicting requirements?

Conflict resolution during ingestion enforces a strict precedence hierarchy: ADR overrides SPEC, which overrides PRD, which overrides general documentation. Unresolved contradictions generate an ingest conflict report and block destination writes.

Can I merge new documentation into an existing .planning/ directory without overwriting locked decisions?

Yes, you can merge new ingested documents into an existing .planning/ setup. The process appends new phases and requirements while hard-blocking any attempts to overwrite or contradict previously locked decisions.

Do I need a manifest file to ingest planning documents by directory convention?

No, you do not need a manifest file. The tool automatically discovers documents using directory conventions like docs/adr or docs/prd, though you can optionally use an explicit manifest to control path, type, and precedence.

What happens to unresolved blockers during documentation ingestion?

Unresolved blockers during documentation ingestion trigger a safety gate that prevents any destination writes. The unresolved cases are documented in an INGEST-CONFLICTS.md report within the .planning/ directory for manual review.