Bootstrap documentation and planning framework

Bootstrap or merge .planning/ from mixed ADRs, PRDs, SPECs, DOCs

Consolidating pre-existing planning documents (ADRs, PRDs, specs) into a GSD project without losing context or forcing new documentation.

• · Directory path (optional, defaults to current)
• · Optional --mode new|merge
• · Optional --manifest <file> listing {path, type, precedence}
• · Optional --resolve auto|interactive (v1 supports auto only)

• · For new: PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md
• · For merge: phases appended to existing ROADMAP.md + requirements merged
• · INGEST-CONFLICTS.md with auto-resolved, competing-variants, unresolved-blockers buckets

• · ingest-docs.md workflow
• · doc-conflict-engine.md
• · gsd-roadmapper (agent delegation)

• · Docs discoverable via convention (docs/adr/, docs/prd/, docs/specs/, docs/rfc/) or manifest
• · Max 50 docs per invocation (v1 constraint)
• · .planning/ absent (new mode) or exists (merge mode)

• · More than 50 docs found → error reported, use manifest to subset
• · Unresolved contradictions exist → BLOCKER gate, no write until conflicts resolved
• · Precedence ambiguous (ADR > SPEC > PRD > DOC) → auto-resolution applied, user reviews INGEST-CONFLICTS.md
• · Merge mode with locked decisions → conflicts highlighted, manual merge required

• · Conflict detection via shared engine (doc-conflict-engine.md)
• · BLOCKER gate prevents write if unresolved contradictions exist
• · Precedence rule applied consistently (ADR > SPEC > PRD > DOC)
• · INGEST-CONFLICTS.md shows all variants and decisions made