reversa-requirements

To generate a requirements document from a vague feature idea, you provide a free-form description, and the system converts it into a complete requirements.md file anchored in existing project architecture and domain context.

Reverse engineering requirements in feature planning means deriving complete specifications by reading legacy artifacts and state management files to anchor new feature requirements in the existing system context.

To prevent overwriting an in-progress feature requirements file, physical artifact detection checks the forward feature directory and prompts you to continue, run in parallel, or abandon the existing work.

Yes, you can use custom hooks before and after generating requirements by configuring before-requirements and after-requirements logic in the hooks.yml file to enrich the processing pipeline.

When handling missing information during requirements generation, the system limits uncertainty markers by inserting specific doubt notations into the requirements.md output to highlight information gaps.

Yes, you need a specific template to output feature requirements, as the system generates the final requirements.md file atomically from a predefined requirements-template.md located in the project directory.