skills.rest
russosalv
russosalvCOMMUNITY
Explore all skills by this author →
GitHub

requirements-ingest

Convert unstructured stakeholder documents into structured Markdown requirement files.

5|Updated Apr 18, 2026
Search Tags:#transcript#pdf#requirements#traceability#docs#docx#ingest
One-click install
npx skills add https://github.com/russosalv/NONoise --skill requirements-ingest-russosalv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-ingest
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/requirements-ingest
Command: npx skills add https://github.com/russosalv/NONoise --skill requirements-ingest-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Raw stakeholder input is noisy, fragmented, and often mixes functional asks with implementation hints, making it hard for architects and product teams to produce a clear, reviewable set of requirements; this skill standardizes and disambiguates that input into traceable requirement documents ready for design.

Core Features & Use Cases

  • Interactive extraction: Reads PDFs, DOCX, markdown notes, emails, and call transcripts to surface atomic candidate requirements with source quotes.
  • Structured output & parking: Proposes domain/feature breakdowns, writes frontmatter-compliant Markdown files under docs/requirements/<domain>/<feature>.md, and copies source documents into per-domain sources folders while preserving originals.
  • Traceability & guardrails: Deduplicates candidates, flags open points and disagreements, prevents silent domain creation, and appends ingestion history for incremental updates.
  • Use case: Hand a collection of kickoff briefs and a meeting transcript to the skill to produce a validated set of draft requirement files that an architect can immediately consume.

Quick Start

Ingest these files and convert them into docs/requirements entries organized by domain and feature: provide the paths to the stakeholder brief and call transcript and confirm the proposed breakdown.

Frequently Asked Questions about requirements-ingest

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

FAQPage Schema
How do I extract requirements from a PDF and call transcript?▼

To extract requirements from a PDF and call transcript, provide the file paths to the skill. It reads unstructured stakeholder documents, surfaces atomic candidate requirements with source quotes, and proposes domain and feature breakdowns for validation.

How do I structure unstructured stakeholder documents into traceable requirement files?▼

Structuring unstructured stakeholder documents involves converting raw input into frontmatter-compliant Markdown files. The skill writes these entries under docs/requirements/<domain>/<feature>.md while parking source documents in per-domain sources folders to preserve traceability.

What is the best way to deduplicate candidate requirements from stakeholder briefs?▼

The best way to deduplicate candidate requirements from stakeholder briefs is to ingest them through an automated extraction process. The skill identifies duplicate candidates, flags open points and disagreements, and appends ingestion history for incremental updates.

Can I use markdown notes and emails to generate domain and feature breakdowns?▼

Yes, you can use markdown notes and emails to generate domain and feature breakdowns. The skill ingests these formats alongside DOCX and PDFs to propose structured organizational hierarchies, preventing silent domain creation during the process.

Does converting raw documents into structured requirements flag open points and disagreements?▼

Converting raw documents into structured requirements does flag open points and disagreements. As it extracts candidate requirements from fragmented input, the skill actively disambiguates the content by highlighting unresolved stakeholder conflicts for review.

Why are my requirements not working when ingesting fragmented stakeholder input?▼

Requirements may not work when ingesting fragmented stakeholder input because the raw data mixes functional asks with implementation hints. Standardizing this noisy input into atomic, traceable requirement files resolves the disambiguation issue for architects.

Related Skills

Explore More Product & Management Skills→
dkyazzentwatwadkyazzentwatwa
86

meeting-notes-formatter

Format raw meeting notes into structured Markdown or PDF documents.

Community
Intermediate
tonehqtonehq
11

generate_feature_prd_and_implementation

Generate a formal feature PRD with requirements, edge cases, and API design into a Markdown file.

Official
Advanced
aurora-atomsaurora-atoms

pr-ready-package

Synthesize code diffs, delivery evidence, and project context into a structured pull request package.

Community
Advanced
rezosndrezosnd

excel-generator

Generate styled Excel workbooks with formulas, charts, and data validation.

Community
Intermediate