gsd-ingest-docs
Bootstraps or merges existing project documentation into a standardized planning format.
Install
mkdir -p .claude/skills/gsd-ingest-docs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13811" && unzip -o skill.zip -d .claude/skills/gsd-ingest-docs && rm skill.zipInstalls to .claude/skills/gsd-ingest-docs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.Key capabilities
- →Scan a repository for ADRs, PRDs, SPECs, and DOCs
- →Bootstrap a new `.planning/` setup
- →Merge documents into an existing `.planning/` setup
- →Classify each document in parallel
- →Synthesize a consolidated context with a conflicts report
- →Route to new-project or merge-milestone based on `.planning/` existence
How it works
The skill scans a repository for various planning documents, classifies them, and synthesizes a consolidated context. It then either bootstraps a new `.planning/` setup or merges into an existing one, generating a conflicts report.
Inputs & outputs
When to use gsd-ingest-docs
- →Bootstrap project planning
- →Consolidating ADRs and specs
- →Generating roadmap documents
About this skill
- Net-new bootstrap (
--mode new, default when.planning/is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation togsd-roadmapper. - Merge into existing (
--mode merge, default when.planning/is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.
Auto-synthesizes most conflicts using the precedence rule ADR > SPEC > PRD > DOC (overridable via manifest). Surfaces unresolved cases in .planning/INGEST-CONFLICTS.md with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.
Inputs: directory-convention discovery (docs/adr/, docs/prd/, docs/specs/, docs/rfc/, root-level {ADR,PRD,SPEC,RFC}-*.md), or an explicit --manifest <file> YAML listing {path, type, precedence?} per doc.
v1 constraints: hard cap of 50 docs per invocation; --resolve interactive is reserved for a future release.
</objective>
<execution_context> @.agent/get-shit-done/workflows/ingest-docs.md @.agent/get-shit-done/references/ui-brand.md @.agent/get-shit-done/references/gate-prompts.md @.agent/get-shit-done/references/doc-conflict-engine.md </execution_context>
<context> $ARGUMENTS </context> <process> Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule. </process>When not to use it
- →When the task exceeds a hard cap of 50 documents per invocation
- →When `--resolve interactive` is required, as it is reserved for a future release
Limitations
- →The skill has a hard cap of 50 documents per invocation
- →The `--resolve interactive` option is reserved for a future release
- →The BLOCKER gate prevents writing destination files if unresolved contradictions exist
How it compares
This skill automates the consolidation and conflict resolution of diverse planning documents into a structured `.planning/` directory, which is more efficient than manual document integration and conflict identification.
Compared to similar skills
gsd-ingest-docs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-ingest-docs (this skill) | 0 | 3mo | No flags | Intermediate |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by SrivarsanK
View all by SrivarsanK →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.