skills.rest
electroheadfx
electroheadfxCOMMUNITY
Explore all skills by this author →
GitHub

gsd-ingest-docs

Generate a .planning/ workspace from ADRs, PRDs, SPECs, RFCs and related docs, handling conflicts by precedence rules.

4|Updated Apr 11, 2026
Search Tags:#planning#adr#spec#conflict resolution#prd#docs ingestion
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-ingest-docs-electroheadfx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ingest-docs
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-ingest-docs
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-ingest-docs-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you gather existing ADRs, PRDs, SPECs, RFCs, and related documentation into a coherent .planning/ workspace, so project decisions and requirements are easier to manage.

Core Features & Use Cases

  • New planning bootstrap: Creates the core planning files when no .planning/ directory exists.
  • Existing plan merge: Adds new phases and requirements into an established planning system while respecting locked decisions.
  • Conflict handling: Detects contradictions, applies precedence rules, and surfaces unresolved blockers for review.
  • Use case: You have a repo with scattered design docs and want a single planning source of truth generated from them in one pass.

Quick Start

Use the gsd-ingest-docs skill to scan this repository’s planning and design documents and build 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 ADRs, PRDs, and RFCs into a single planning workspace?▼

You can consolidate scattered ADRs, PRDs, and RFCs by ingesting existing documentation to automatically generate or merge a structured `.planning/` workspace. This creates a single source of truth for project decisions and requirements.

Can I merge new design docs into an existing planning system without overwriting locked decisions?▼

Merging new design docs respects locked decisions in an existing planning system by applying precedence-aware synthesis. The workflow adds new phases and requirements while safely handling blockers and surfacing unresolved conflicts for review.

What is the best way to bootstrap project planning for a repository with unstructured design documents?▼

Bootstrapping project planning from unstructured design documents involves scanning existing files to create core planning artifacts. This generates a coherent `.planning/` directory from scratch, even when no prior planning structure exists.

How does conflict detection work when ingesting multiple project requirements documents?▼

Conflict detection during ingestion works by applying precedence rules to identify contradictions across discovered source files. It safely handles blockers by surfacing unresolved conflicts for manual review rather than auto-resolving them.

Do I need a specific document format to ingest PRDs and SPECs into a planning setup?▼

You can ingest standard PRDs, SPECs, and related documentation regardless of specific formatting. The ingestion process scans the repository to discover these source files and synthesizes them into structured planning artifacts.

What are the limitations of automating planning document ingestion from scattered repository files?▼

A limitation of automating planning document ingestion is that it cannot auto-resolve every contradiction. While it applies precedence rules, it must surface unresolved blockers for manual review to ensure decision integrity.

Related Skills

Explore More Software Engineering Skills→
yusaduymazyusaduymaz

gsd-ingest-docs

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

Community
Advanced
devCharuzudevCharuzu

scrum-master

Analyze sprint data to forecast velocity and generate health scores.

Community
Advanced
xingBaGanxingBaGan

approve-whitepaper

Validate whitepaper drafts and promote them to locked versions.

Community
Intermediate
kriscardkriscard
13

Obsidian Workflows & Second Brain Methodology

Organize Obsidian vaults using PARA and PKM patterns.

Community
Advanced