Ingest ADR, PRD, SPEC, and DOC files into a repo's .planning/ system.
npx skills add https://github.com/deerawan/dotfiles --skill gsd-ingest-docs-deerawan
Please help me install this Agent Skill. Skill: gsd-ingest-docs Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-ingest-docs Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-ingest-docs-deerawan
It solves the problem of turning scattered product thinking—ADRs, PRDs, SPECS, and other documentation—into a coherent, working .planning/ system without manually stitching everything together.
.planning/ system: Synthesizes PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md from ingested docs when .planning/ is missing, delegating final synthesis to gsd-roadmapper..planning/: Appends phases and requirements derived from new ingested docs while preserving prior decisions.ADR > SPEC > PRD > DOC, writes .planning/INGEST-CONFLICTS.md, and hard-blocks writes when unresolved contradictions exist via the BLOCKER gate.--manifest file that lists {path, type, precedence?} per doc.Run gsd-ingest-docs with your repo path to generate a complete .planning/ setup from existing ADRs, PRDs, SPECS, and docs.
High-intent search queries and answers about installing and using this skill.
To consolidate scattered ADRs, PRDs, and SPECS, this tool ingests multiple documents and synthesizes them into a structured .planning/ directory. It automatically generates PROJECT.md, REQUIREMENTS.md, and ROADMAP.md files from your existing product documentation.
Conflicts when merging product requirements are resolved using a deterministic precedence rule where ADR overrides SPEC, which overrides PRD, then DOC. Unresolved contradictions are written to INGEST-CONFLICTS.md and a BLOCKER safety rule prevents any writes until they are fixed.
You can merge new requirements into an existing .planning/ directory without losing prior decisions. The tool appends newly derived phases and requirements from ingested docs while preserving the established project timeline and historical planning artifacts.
The maximum number of documents you can synthesize during a single documentation ingestion is 50 per invocation. This operational constraint ensures reliable processing when bootstrapping a new planning system or merging additional product decisions.
You do not need a manifest file to ingest product planning documents. The tool automatically discovers documents from conventional repository paths, but you can optionally provide an explicit --manifest file to specify exact paths and precedence levels for each document.
FerroxLabsBuild a planning workspace from existing ADR, PRD, SPEC, DOC, and RFC files.
nnexaiSynthesize ADRs, PRDs, and specifications into a standardized .planning/ directory.
rkz91Create and update milestone planning documents and route to the requirements phase.
mcampbellrBootstrap or merge .planning/ setups from ADRs, PRDs, SPECs, and DOCs.