gsd-ingest-docs

To bootstrap a .planning directory from existing ADRs and PRDs, you can run an ingestion process that synthesizes documents into PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md. It discovers inputs via standard doc directories or an explicit manifest.

The precedence order for resolving conflicts when ingesting specs and requirements is ADR > SPEC > PRD > DOC. The system applies deterministic conflict detection and reports unresolved blockers to a dedicated conflict file.

To merge new requirements into an existing .planning setup safely, the ingestion process appends new phases while hard-blocking contradictions with locked decisions. A BLOCKER rule prevents writing destination files when unresolved contradictions exist.

Yes, you can use a custom manifest to define document paths and types for planning automation. The system accepts an explicit --manifest YAML file to define doc paths, types, and precedence instead of relying on directory conventions.

The primary limitation of ingesting planning documents in a single run is a hard v1 cap of 50 documents per invocation. Additionally, a BLOCKER rule halts the process if unresolved contradictions are detected among the inputs.

Roadmap generation when synthesizing requirements from repository docs works by consolidating content into a ROADMAP.md file. The ingestion process generates the foundational planning artifacts and delegates the final roadmap writing to a specialized roadmapping component.