skills.rest
LucasBiason
LucasBiasonCOMMUNITY
Explore all skills by this author →
GitHub

requirements-extractor

Extract structured functional requirements, actors, flows, and assumptions from unstructured text.

Updated Aug 27, 2026
Search Tags:#specification#requirements#assumptions#traceability#functional-requirements#open-questions#unstructured-input
One-click install
npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill requirements-extractor-lucasbiason
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-extractor
Source: https://github.com/LucasBiason/engineering-knowledge-base/tree/main/.claude/skills/workflow/requirements-extractor
Command: npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill requirements-extractor-lucasbiason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts unstructured input (plain text, notes, partial docs) into structured functional requirements, actor definitions, and open questions without inventing requirements.

Core Features & Use Cases

  • Extract functional requirements (FR-xxx) from messy input with traceable IDs.
  • Identify actors, flows, knowns/unknowns, and assumptions to support PRD creation.
  • Generate clean, testable outputs ready for documentation and validation.

Quick Start

Paste your raw notes or meeting summaries to generate FRs, actors, flows, unknowns, and assumptions.

Frequently Asked Questions about requirements-extractor

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

FAQPage Schema
How do I extract functional requirements from unstructured meeting notes?▼

To extract functional requirements from unstructured notes, paste raw text or meeting summaries to generate testable atomic requirements. The tool outputs structured FR-xxx definitions with traceable IDs to canonical spec locations.

What is the best way to identify assumptions and open questions from partial documents?▼

Identifying assumptions and open questions from partial documents involves parsing text to separate knowns and unknowns. This tool outputs structured lists of assumptions and open questions to canonical spec locations for validation.

Can I generate traceable specifications from plain text tickets without inventing new requirements?▼

Yes, you can generate traceable specifications from plain text tickets without inventing new requirements. The tool enforces strict extraction rules, producing only testable atomic outputs based solely on the provided input.

Does the requirements extraction process support actor and flow definitions for PRD creation?▼

Yes, the requirements extraction process supports PRD creation by identifying actors and flows from messy input. It generates clean outputs including actor definitions and flows ready for documentation.

What are the limitations of automated requirement extraction from unstructured input?▼

A key limitation of automated requirement extraction is that it cannot invent missing details. It strictly enforces a no-invention rule, structuring only explicitly stated information and flagging unknowns rather than filling gaps.

Related Skills

Explore More Software Engineering Skills→
beshkenadzebeshkenadze
3

meeting-notes

Convert meeting transcripts into structured notes with decisions and action items.

Community
Basic
owainlewisowainlewis
294

requirements

Transform rough notes into a structured REQUIREMENTS.md document.

Community
Intermediate
ilandahanilandahan
9

aid-prd

Convert discovery insights into a PRD with user stories and traceability matrix.

Community
Advanced
maggitmaggit

requirements

Extract and structure requirements from unstructured input into a PRD-ready document.

Community
Intermediate