reverse-requirements

Extract EARS-style requirements from SCN-*.md scene documents.

52|3|Updated Feb 14, 2026

Search Tags:#automation #documentation #requirements #analysis #scene #ears

Ready to run

npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill reverse-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-requirements
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/reverse-requirements
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill reverse-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms scenario documents into structured, executable requirements and organizes them into independent, trackable files using the EARS format to guide development.

Core Features & Use Cases

Scene-driven analysis converts SCN-XXX-*.md into functional requirements using EARS syntax.
Automated splitting of requirements into discrete files under omni-doc/specs/requirements with consistent naming.
Supports caching, path filtering, and interactive prompts for staged workflow execution.

Quick Start

Point the tool at your project root and run the reverse analysis to generate initial requirements from scene documents.

Frequently Asked Questions about reverse-requirements

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

FAQPage Schema

How do I automate extracting requirements from scenario documents?▼

To automate requirement extraction from scenario documents, the tool analyzes SCN-*.md files and converts them into EARS-style functionality requirements. It parses scene-driven project files and structures them into trackable, executable specifications.

What is the EARS syntax for structuring executable requirements?▼

EARS syntax is a structured format for writing executable requirements. The tool applies EARS to transform scenario documents into discrete, independent requirement files, ensuring outputs follow predefined templates for development guidance.

How do I split a large requirement document into independent files?▼

To split requirements into independent files, the tool performs automated splitting of generated EARS specifications. It places these discrete files under the omni-doc/specs/requirements directory with consistent naming conventions for tracking.

Does this requirements analysis tool support staged workflow execution?▼

Yes, the requirements analysis tool supports staged workflow execution. It utilizes caching, path filtering, and interactive prompts to process scenario documents incrementally, while a cache-aware state machine records progress.

Can I use this scene-driven analysis for projects outside of software engineering?▼

Yes, you can use scene-driven analysis for projects outside of software engineering. The tool applies to scenario-driven projects across domains, converting SCN-XXX-*.md documents into structured EARS requirements.