reversa-requirements

To convert a rough product idea into a formal requirements document, describe the feature concept in natural language and invoke the skill to automatically generate structured requirements with sections, traceability, and artifact references.

Generating requirements that trace back to existing reverse pipeline artifacts involves reading and interpreting .reversa/state.json and setup configurations, then anchoring the newly generated requirements.md to those specific reverse workflow states for consistent product handoff.

Yes, you can use natural language user stories to draft feature design specifications. The skill captures free-form ideas or sentences and transforms them into complete formal specifications required for design, development, and QA processes.

The best way to structure product management requirements from a free-form concept is to validate alignment with existing reverse artifacts and generate a requirements.md file that proposes structured next steps for the development pipeline.

You do not strictly need existing files to generate product requirements, but the skill validates alignment with .reversa/state.json and .reversa/setup.json if present, ensuring the generated requirements integrate properly with the reverse engineering workflow and propose accurate next steps.