reverse-requirements

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.

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.

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.

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.

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.