gsd-ingest-docs

Ingest repository planning documents and generate PROJECT, REQUIREMENTS, ROADMAP, and STATE outputs.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-ingest-docs-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-ingest-docs
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-ingest-docs-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered planning documents into a structured .planning setup, reducing the manual effort needed to reconcile decisions, requirements, and roadmap artifacts across a repository.

Core Features & Use Cases

  • Document Ingestion: Collects ADRs, PRDs, SPECs, RFCs, and supporting docs from common repository locations.
  • Planning Synthesis: Builds or merges PROJECT, REQUIREMENTS, ROADMAP, and STATE outputs from the source material.
  • Conflict Handling: Detects contradictions, applies precedence rules, and surfaces unresolved blockers for review.
  • Use Case: A product or engineering team can point the skill at a repo full of design notes and planning docs and get a consistent, conflict-aware planning workspace.

Quick Start

Ask the skill to ingest the repository’s planning documents and generate or merge the .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 ADR, PRD, and RFC docs into a single planning workspace?

To consolidate scattered ADR, PRD, and RFC docs, ingest repository documentation to automatically build a structured .planning workspace. This process collects design notes and synthesizes them into PROJECT, REQUIREMENTS, ROADMAP, and STATE outputs.

What is the best way to handle conflicting decisions across multiple RFC and SPEC files?

Handling conflicting decisions across RFC and SPEC files requires precedence-aware conflict detection. The system applies precedence rules to identify contradictions and surfaces unresolved blockers for manual review.

How do I generate a project roadmap from existing planning documents in a repository?

To generate a project roadmap from existing planning documents, ingest ADRs, PRDs, and SPECs from common repository locations. The synthesis process extracts milestones and requirements to automatically produce a ROADMAP artifact.

Can I merge new design notes into an existing .planning setup without losing previous decisions?

You can merge new design notes into an existing .planning setup without losing previous decisions by applying precedence-aware conflict handling. The system detects contradictions between new and existing artifacts and merges them safely.

Does this planning synthesis approach work for repositories without standardized documentation folders?

This planning synthesis approach targets repositories with ADR, PRD, SPEC, and RFC files in common locations. Repositories lacking standardized planning documentation folders may not provide sufficient source material for generating structured outputs.