Verified:GitHub

reversa-requirements

Transform a feature idea into a requirements.md anchored to Reversa pipeline artifacts.

1|Updated Nov 20, 2025

Search Tags:#workflow #specification #requirements #traceability #product-management #reverse-engineering #feature-definition

Ready to run

npx skills add https://github.com/stribus/pygerengastos --skill reversa-requirements-stribus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-requirements
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-requirements
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-requirements-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms vague feature ideas into a complete, formal requirements document anchored to the Reversa pipeline artifacts, enabling consistent handoffs and traceability.

Core Features & Use Cases

Generates a full requirements document (requirements.md) from a free-form idea, anchored to existing Reversa state and artifacts.
Reads project context (state.json, hooks.yml, and related assets) to ensure alignment with current workflows and governance.
Produces a structured, ready-to-use document suitable for reviews, planning, and archiving.

Quick Start

Provide a brief idea or feature description and I will generate a complete requirements document anchored to the Reversa pipeline.

Frequently Asked Questions about reversa-requirements

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

FAQPage Schema

How do I convert a vague product idea into a formal requirements specification?▼

To convert a vague idea into a formal requirements specification, you provide a free-form feature description and the system generates a structured requirements.md document. This document applies formatting, traceability, and auditability rules to ensure it is ready for planning and reviews.

What is requirements traceability and when do I need it for feature definition?▼

Requirements traceability links formal feature definitions back to existing system artifacts and pipeline state. You need it when transforming new ideas into structured specifications, ensuring every requirement aligns with current workflows and maintains auditability for formal reviews.

How do I generate a requirements document from an idea using reverse-engineering artifacts?▼

You generate a requirements document by providing a brief feature description, which the system then anchors to existing reverse-engineering artifacts. It reads project context like state.json and hooks.yml to produce a comprehensive, ready-to-use requirements.md file.

Do I need existing pipeline artifacts to create a traceable requirements document?▼

Yes, creating a traceable requirements document relies on existing pipeline artifacts. The system reads project context such as state.json and hooks.yml to anchor the new specification, ensuring the generated requirements.md aligns with current workflows and governance.

Can I use this for new feature ideas across different product domains?▼

Yes, this process applies to new feature ideas across product domains. It guides the creation of a formal requirements specification from vague input, generating a comprehensive document anchored to reverse-engineering artifacts regardless of the specific product area.

Why does my generated requirements document need to reference system artifacts?▼

Your generated requirements document references system artifacts to enforce formatting, traceability, and auditability. Anchoring the specification to existing pipeline state and assets ensures consistent handoffs and alignment with current project workflows and governance.