Ingest ADR, PRD, SPEC, and DOC files into .planning/ workflows.
npx skills add https://github.com/aslaii/dotfiles --skill gsd-ingest-docs
Please help me install this Agent Skill. Skill: gsd-ingest-docs Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-ingest-docs Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-ingest-docs
Ingest planning documents from ADRs, PRDs, SPECs, and DOCs to bootstrap or merge a .planning/ setup across a repository, synthesizing context and surfacing conflicts for resolution.
Run the ingest-docs workflow with the path to your repository to bootstrap or merge .planning/.
High-intent search queries and answers about installing and using this skill.
To bootstrap a .planning setup from scattered PRDs and ADRs, ingest planning documents from standard locations to auto-generate PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md. The workflow processes multiple doc types in parallel and classifies them by precedence.
When conflicting requirements exist across SPECs and PRDs, the ingest workflow auto-synthesizes conflicts using the precedence ADR > SPEC > PRD > DOC. It outputs INGEST-CONFLICTS.md with categorized results and gates writes to prevent blockers from proceeding.
You can merge new architecture decision records into an existing planning setup by running the ingest workflow. It appends new phases and requirements to your current .planning/ directory instead of overwriting it, preserving existing project state.
You can process up to 50 planning documents in a single ingest run. The workflow enforces a 50-doc cap per execution to manage processing loads when classifying standard locations like docs/specs/ and root-level RFC files.
You do not need a manifest to control document precedence during planning ingestion, as the default ADR > SPEC > PRD > DOC hierarchy applies automatically. However, providing an optional manifest input allows you to manually control routing and precedence.
The best way to consolidate RFCs and SPECs into a single roadmap is to run a parallel ingest workflow that classifies documents by precedence. This synthesizes scattered context and outputs a unified ROADMAP.md alongside your core planning files.
lgwanaiIngest ADRs, PRDs, and SPECs into a repository-level .planning/ structure.
thecomputer07Archives completed milestone docs and updates ROADMAP.md, REQUIREMENTS.md, STATE.md for the next version.
jedmamostoCoordinate milestone phases from a terminal dashboard using GSD commands.
ThiagoVitaleCreate or merge a .planning/ directory from ADRs, PRDs, SPECs, and other documents with precedence-based conflict resolution.
