gsd-ingest-docs

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

1|Updated Apr 4, 2026

Search Tags:#workflow #planning #documentation #adr #synthesis #prd

Ready to run

npx skills add https://github.com/nnexai/git-stacks --skill gsd-ingest-docs-nnexai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-ingest-docs
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-ingest-docs-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the fragmentation of project documentation by automatically synthesizing disparate ADRs, PRDs, and specifications into a unified, structured .planning/ directory.

Core Features & Use Cases

Automated Synthesis: Automatically generates project artifacts like PROJECT.md, REQUIREMENTS.md, and ROADMAP.md from existing documentation.
Conflict Resolution: Uses a precedence-based engine to resolve contradictions between documents while flagging unresolved blockers for manual review.
Use Case: When joining a new project with scattered design and requirement docs, use this skill to instantly create a coherent project roadmap and state tracking system.

Quick Start

Invoke the gsd-ingest-docs skill to scan the current repository and bootstrap a new planning setup.

Frequently Asked Questions about gsd-ingest-docs

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

FAQPage Schema

How do I consolidate scattered ADRs and PRDs into a single planning directory?▼

To consolidate scattered ADRs and PRDs, you can synthesize existing project documentation into a standardized .planning/ directory structure. This process automatically discovers files via directory conventions and generates unified artifacts like PROJECT.md and ROADMAP.md.

How does conflict resolution work when merging project documentation?▼

Conflict resolution when merging project documentation uses a precedence-based engine to resolve contradictions between disparate documents. Unresolved blockers are automatically flagged for manual review to ensure planning accuracy.

Can I bootstrap a project roadmap from existing specifications without manual writing?▼

Yes, you can bootstrap a project roadmap from existing specifications without manual writing. The skill automates the generation of project artifacts like REQUIREMENTS.md and ROADMAP.md directly from your current repository's documentation.

Do I need gsd-roadmapper to generate planning artifacts from existing docs?▼

Yes, generating planning artifacts from existing docs requires integration with gsd-roadmapper. This integration ensures proper synthesis of project specifications into the .planning/ directory while adhering to strict safety gates.

What are the limitations of automated documentation synthesis for project planning?▼

Automated documentation synthesis for project planning is limited by its inability to resolve all document contradictions autonomously. Precedence-based conflict resolution flags unresolved blockers, requiring manual review to maintain planning accuracy.