Ingest ADRs, PRDs, and SPECs into a repository-level .planning/ structure.
npx skills add https://github.com/lgwanai/openforce --skill gsd-ingest-docs-lgwanai
Please help me install this Agent Skill. Skill: gsd-ingest-docs Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-ingest-docs Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-ingest-docs-lgwanai
This Skill turns scattered ADRs, PRDs, SPECs, and other repository documents into a coherent .planning/ workspace, so teams can quickly align on requirements, roadmaps, and state without manual restructuring.
.planning/ is absent, synthesizes PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md, delegating the roadmap generation to gsd-roadmapper..planning/ exists, appends phases and requirements derived from ingested docs while blocking contradictions with locked decisions.ADR > SPEC > PRD > DOC (overridable via a manifest) and writes unresolved results to .planning/INGEST-CONFLICTS.md, using a BLOCKER gate to prevent writing destination files when unresolved contradictions exist.docs/adr/, docs/prd/, docs/specs/, docs/rfc/, and root-level {ADR,PRD,SPEC,RFC}-*.md) or ingests an explicit manifest file via --manifest <file>.Run the Skill in net-new mode to build a full .planning/ setup from your repository’s ADRs, PRDs, SPECs, and docs, using default discovery conventions.
High-intent search queries and answers about installing and using this skill.
When conflict resolution is applied during planning setup, ingestion auto-resolves contradictions using precedence rules where ADR overrides SPEC, SPEC overrides PRD, and PRD overrides DOC. Unresolved contradictions are written to `INGEST-CONFLICTS.md` and a BLOCKER gate prevents destination file writes until fixed.
You can ingest an explicit manifest file using the `--manifest <file>` flag to specify exact documents for ingestion. Without a manifest, the tool auto-discovers documents from conventional repository paths like `docs/adr/`, `docs/prd/`, and root-level `ADR-*.md` files.
If your repository lacks a `.planning/` directory, running the net-new bootstrap creates the entire structure from discovered documents. If the directory already exists, it performs a safe incremental merge, appending new phases and requirements while enforcing conflict precedence to protect locked decisions.
To prevent corrupting your planning setup, a BLOCKER gate stops the tool from writing destination files when unresolved contradictions exist. You must manually resolve the conflicts listed in `.planning/INGEST-CONFLICTS.md` before the synthesis can complete successfully.
During net-new bootstrap, roadmap generation is delegated to `gsd-roadmapper` after synthesizing the initial planning files. This ensures the generated `ROADMAP.md` aligns with the newly extracted requirements and project state.
The BLOCKER gate enforces this by halting all destination file writes and surfacing the unresolved issues in `.planning/INGGEST-CONFLICTS.md`. You must resolve these documented conflicts before the tool can safely append phases and requirements to your existing planning structure.
electroheadfxGenerate a .planning/ workspace from ADRs, PRDs, SPECs, RFCs and related docs, handling conflicts by precedence rules.
cshyangGenerate a phased roadmap with phases and waves in ROADMAP.md.
CharlieGreenmanInitialize research milestone artifacts and roadmap from project context.
mcampbellrBootstrap or merge .planning/ setups from ADRs, PRDs, SPECs, and DOCs.