reversa-drafter

To generate a PRD from ideation and personas, the Skill reads ideation.md and personas.md from your output folder, synthesizing them into a complete prd.md document with problem definition, metrics, scope, risks, and acceptance criteria.

Missing information during product requirements drafting is explicitly marked as [INDEFINIDO, validar com usuário] instead of being artificially generated, ensuring a pending validation section for human review of undefined gaps.

Yes, you need a .reversa/state.json file because the PRD generation process reads it to determine the correct output paths before writing the final prd.md file to your designated output folder.

Yes, you can define metrics, non-goals, constraints, and dependencies for an AI agent workflow because the output PRD is structured to be both human-readable and agent-readable for aligned product definition.

The best way to consolidate product ideation into actionable requirements is combining ideation.md and personas.md to output a structured PRD covering 9 sections, including scope, constraints, dependencies, and high-level acceptance criteria.

The PRD drafter leaves gaps marked as undefined to validate with the user instead of inventing content, ensuring the generated product requirements document remains factually accurate and highlighting specific areas needing human input.