skills.rest
FerroxLabs
FerroxLabsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ferrox-ingest-docs

Build a planning workspace from existing ADR, PRD, SPEC, DOC, and RFC files.

21|9|Updated Jul 21, 2026
Search Tags:#planning#documentation#roadmap#conflict resolution#specs#prds#adrs
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ingest-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ferrox-ingest-docs
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-ingest-docs
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ingest-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps when you already have ADRs, PRDs, specs, or RFCs and need them converted into a structured planning workspace instead of being rewritten by hand.

Core Features & Use Cases

  • Plan bootstrap: Creates a new .planning/ structure from existing documents, including project, requirements, roadmap, and state files.
  • Plan merge: Appends new phases and requirements into an existing planning setup while respecting locked decisions.
  • Conflict handling: Detects contradictions, classifies them, and blocks unsafe writes until blockers are resolved.
  • Use case: A team can drop a folder of design docs and immediately generate a coherent execution plan with traceable conflicts and precedence rules.

Quick Start

Use the ferrox-ingest-docs skill to ingest my planning documents from the specified path and build or merge the .planning/ workspace safely.

Frequently Asked Questions about ferrox-ingest-docs

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

FAQPage Schema
How do I turn existing ADRs, PRDs, and specs into a structured planning workspace?▼

Plan bootstrap builds a new `.planning/` structure from existing documents by creating project, requirements, roadmap, and state files, while plan merge appends new phases into an existing setup and respects locked decisions to prevent unsafe overwrites.

How do I handle conflicting requirements when merging multiple RFCs and PRDs?▼

Plan merge appends new phases and requirements into an existing planning setup while respecting locked decisions, detecting contradictions, and classifying them to block unsafe writes until blockers are resolved.

Can I use existing design docs to generate a roadmap without rewriting them?▼

Yes, the bootstrap workflow synthesizes roadmap and requirements artifacts directly from discovered ADR, PRD, SPEC, DOC, and RFC files instead of rewriting them, generating a coherent execution plan with traceable conflicts.

What is the best way to append new phases to an existing project plan without overwriting locked decisions?▼

The best way is using a plan merge workflow that appends new phases and requirements into an existing planning setup while respecting locked decisions and applying precedence handling and blocker-safe output generation before writing files.

Do I need a manifest file to list planning documents for ingestion?▼

You do not strictly need a manifest file, as the workflow applies to both discovered documents and manifest-listed files to build or merge the `.planning/` workspace safely.

Related Skills

Explore More Software Engineering Skills→
jedmamostojedmamosto

gsd-ingest-docs

Ingest ADRs, PRDs, SPECs, and docs into .planning/ artifacts with conflict detection.

Community
Advanced
nnexainnexai
1

gsd-add-phase

Add project phases to roadmaps with sequential identifiers and state files.

Community
Intermediate
yusaduymazyusaduymaz

gsd-ingest-docs

Ingest repository planning documents and generate PROJECT, REQUIREMENTS, ROADMAP, and STATE outputs.

Community
Advanced
electroheadfxelectroheadfx
4

gsd-ingest-docs

Generate a .planning/ workspace from ADRs, PRDs, SPECs, RFCs and related docs, handling conflicts by precedence rules.

Community
Advanced