How do I install the Req Ext skill?

Run npx skillmds@latest add mxsmirnov/req-ext in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Req Ext safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Req Ext?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Req Ext free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Req Ext?

mxsmirnov (@mxsmirnov) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Req Ext by mxsmirnov — Agent Skill

Name: Req Ext
Author: mxsmirnov

Req Ext

Extracts well-formed requirements from unstructured text per ISO/IEC/IEEE 29148:2011, Section 5.2.4 (Figure 1). Saves results to `req.md`. Output is in Russian; table column headers remain in English. Use when transforming raw text into structured, verifiable requirements.

mxsmirnov Updated Sep 22, 2026

File contents

Purpose

Transform raw text into structured requirements stored in req.md. Requirement text and notes are in Russian. Column headers remain in English: #, Condition, Subject, Action, Object, Constraint.

How It Works

Input: Unstructured text describing needs, constraints, or capabilities.
Parse: Split into sentences/clauses expressing requirements.
Extract: Identify or infer Condition, Subject, Action, Object, and Constraint. Mark missing parts as (нет) or (не указано).
Table: Number requirements and present them in a Markdown table.
Persistence: Write to req.md, overwriting existing content. Follow the template in assets/req-template.md.
Notes: Add a rationale section in Russian for ambiguous cases.

Instructions

When the user provides text:

Parse and extract requirements as described above.
Display the table in the conversation and write it to req.md.
Add notes explaining inferences, splits, or ambiguities.
If information is missing, flag the requirement as "Incomplete" and suggest what is needed.

What the Skill Does NOT Do

Invent requirements not present in the source.
Perform validation or prioritization unless instructed.
Generate design solutions.

Additional Guidance

Prefer active voice; avoid negative statements.
Keep each requirement singular (one action per requirement).
Flag vague terms and suggest measurable alternatives.
Design constraints are extracted but noted as such.

Contact

Refer to ISO/IEC/IEEE 29148 or the requirements engineering team.

---name: req-extdescription: Extracts well-formed requirements from unstructured text per ISO/IEC/IEEE 29148:2011, Section 5.2.4 (Figure 1). Saves results to `req.md`. Output is in Russian; table column headers remain in English. Use when transforming raw text into structured, verifiable requirements.---# PurposeTransform raw text into structured requirements stored in `req.md`. Requirement text and notes are in Russian. Column headers remain in English: `#`, `Condition`, `Subject`, `Action`, `Object`, `Constraint`.# How It Works1. **Input**: Unstructured text describing needs, constraints, or capabilities.2. **Parse**: Split into sentences/clauses expressing requirements.3. **Extract**: Identify or infer `Condition`, `Subject`, `Action`, `Object`, and `Constraint`. Mark missing parts as `(нет)` or `(не указано)`.4. **Table**: Number requirements and present them in a Markdown table.5. **Persistence**: Write to `req.md`, overwriting existing content. Follow the template in `assets/req-template.md`.6. **Notes**: Add a rationale section in Russian for ambiguous cases.# InstructionsWhen the user provides text:1. Parse and extract requirements as described above.2. Display the table in the conversation and write it to `req.md`.3. Add notes explaining inferences, splits, or ambiguities.4. If information is missing, flag the requirement as "Incomplete" and suggest what is needed.# What the Skill Does NOT Do- Invent requirements not present in the source.- Perform validation or prioritization unless instructed.- Generate design solutions.# Additional Guidance- Prefer active voice; avoid negative statements.- Keep each requirement singular (one action per requirement).- Flag vague terms and suggest measurable alternatives.- Design constraints are extracted but noted as such.# ContactRefer to ISO/IEC/IEEE 29148 or the requirements engineering team.

Frequently asked questions