ingest-docs

Parse Markdown inputs into gap-analysis, prd-structure, and task_hints YAML artifacts.

1|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ezagent42/prd2impl --skill ingest-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest-docs
Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-0-ingest
Command: npx skills add https://github.com/ezagent42/prd2impl --skill ingest-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests heterogeneous Markdown documents into unified YAML artifacts for downstream PRD tooling, enabling teams to convert hand-authored gap analyses, design specs, plans, and PRDs into a consistent data model.

Core Features & Use Cases

  • Ingest multiple Markdown files and classify them into standardized YAML artifacts (gap-analysis, prd-structure, task_hints) for downstream task generation and validation.
  • Preserve human design decisions by exporting a task_hints.yaml that captures file changes and implementation steps.
  • Use when onboarding a new project with existing MD docs, or when migrating from manual PRD analysis to automated pipeline.

Quick Start

Ingest your Markdown docs to produce YAML artifacts for PRD planning.

Frequently Asked Questions about ingest-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Markdown docs into YAML for PRD pipeline ingestion?

To convert Markdown docs into YAML for PRD pipeline ingestion, use this Skill to parse heterogeneous inputs and generate standardized artifacts like gap-analysis.yaml, prd-structure.yaml, and task_hints.yaml for downstream tooling.

What is the best way to structure hand-authored gap analyses and design specs for automated task generation?

The best way to structure hand-authored gap analyses and design specs is to ingest them into a unified YAML data model, preserving human design decisions in task_hints.yaml to ensure traceable, machine-friendly outputs for automated task generation.

Can I ingest multiple Markdown files into a single PRD structure at once?

Yes, you can ingest multiple Markdown files at once. The Skill classifies heterogeneous documents into standardized YAML artifacts, producing a consolidated prd-structure.yaml for downstream validation and task planning.

Do I need an existing ingestion pipeline to extract PRD structure and task hints from Markdown?

Yes, the Skill requires the ingestion pipeline—comprising gap analysis, PRD extraction, and cross-validation—to process the Markdown inputs and produce the final gap-analysis.yaml, prd-structure.yaml, and task_hints.yaml artifacts.

When should I use Markdown ingestion for PRD planning instead of manual analysis?

Use Markdown ingestion for PRD planning when onboarding a new project with existing MD docs or migrating from manual PRD analysis to an automated pipeline, ensuring consistent data models and traceable outputs across files.

Why does my Markdown ingestion not working for downstream task generation?

Markdown ingestion may fail for downstream task generation if the required pipeline steps—gap analysis, PRD extraction, and cross-validation—are not properly configured to output the gap-analysis.yaml, prd-structure.yaml, and task_hints.yaml artifacts.