Normalize PRDs, RFCs, diagrams, and wiki exports into a repo-grounded intake index.
npx skills add https://github.com/iadr-dev/colab --skill document-intake
Please help me install this Agent Skill. Skill: document-intake Source: https://github.com/iadr-dev/colab/tree/main/skills/document-intake Command: npx skills add https://github.com/iadr-dev/colab --skill document-intake
It prevents teams from wasting time aligning on requirements scattered across PRDs, RFCs, wiki exports, and pasted snippets by normalizing them into a traced, repo-grounded intake artifact.
.ohc/PROJECT.md, compares claims to the codebase, and records conflicts, stale sections, and gaps without hiding uncertainty..ohc/doc-sources.md using assets/doc-sources.template.md, creating a single index that agents use to plan and implement.Ask your agent to run document-intake for an external PRD set of links so it produces .ohc/doc-sources.md and a plan covering unresolved conflicts.
High-intent search queries and answers about installing and using this skill.
Normalizing scattered PRDs and RFCs involves inventorying all provided paths and URLs, tagging each with a requirement role, and reconciling claims against the codebase to produce a canonical `.ohc/doc-sources.md` index.
Document intake is the process of consolidating external specifications like wiki exports and diagrams into a repo-grounded artifact that captures source roles, identifies staleness, and prepares a gated handoff plan.
Reconciling external requirements against your codebase involves loading `.ohc/PROJECT.md`, comparing incoming claims to the existing repository state, and explicitly recording unresolved conflicts, stale sections, and gaps.
Yes, document intake supports repeated specifications updates by continuously writing and updating a canonical `.ohc/doc-sources.md` index, allowing subsequent intakes to append or reconcile new sources.
Handling requirement conflicts before implementation planning involves generating a gated handoff plan under `.ohc/plans/` that includes unresolved questions and blocks build execution until user confirmation.
Yes, document intake requires a build gate for execution because it produces a narrowed writing-plans handoff that blocks implementation until the user reviews conflicts and explicitly confirms.
iadr-devAnalyze session logs to compare planned versus actual outcomes and extract reusable patterns.
iadr-devExecute PLAN, BUILD, and REVIEW coding workflows with human approval gates.
mohamedgshoaibGenerates README files from scanned repository contents and metadata.
cenconq25Detects PRD-ADR coverage gaps and conflicts, returning a PASS/CONCERNS/FAIL verdict and traceability matrix without modifying files.