visa-redator

Convert conceptual domain models into canonical SDD artifacts for paridade-guard validation.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Adgmed2018/visa --skill visa-redator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visa-redator
Source: https://github.com/Adgmed2018/visa/tree/main/agents/visa-redator
Command: npx skills add https://github.com/Adgmed2018/visa --skill visa-redator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transforms the conceptual domain model from Modelador into executable, canonically structured SDD artifacts (e.g., BR-FUTURE and BR-DESCARTAR) that paridade-guard can validate and enforce.

Core Features & Use Cases

  • Generates _visa_sdd/business_model.md in canonical Reversa-compatible format with stable BR-FUTURE IDs and BR-DESCARTAR entries.
  • Produces _visa_sdd/discard_log.md and _visa_sdd/ambiguity_log.md to document decisions and uncertainties.
  • Outputs alignment artifacts that mirror the forward Writer/Curator roles in Reversa and map evidence to rules.

Quick Start

Feed the conceptual model outputs to the redactor and obtain canonical artifacts (business_model.md, discard_log.md, ambiguity_log.md) ready for paridade-guard validation.

Frequently Asked Questions about visa-redator

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

FAQPage Schema
How do I convert a domain model into executable SDD specifications?

To convert a domain model into executable SDD specifications, you feed conceptual domain model outputs into a redactor to generate canonical business_model.md artifacts with stable BR-FUTURE IDs and BR-DESCARTAR entries for automated validation.

What is the best way to generate business rules from domain concepts for automated validation?

Generating business rules from domain concepts for automated validation involves transforming conceptual models into canonical SDD artifacts, producing BR-FUTURE and BR-DESCARTAR IDs that map evidence to rules for paridade-guard verification.

How do I document ambiguities and discarded decisions when creating executable specs?

To document ambiguities and discarded decisions when creating executable specs, you generate discard_log.md and ambiguity_log.md files alongside the business model to track uncertainties and document decision rationale.

Do I need a conceptual domain model before generating canonical SDD artifacts?

Yes, generating canonical SDD artifacts requires a conceptual domain model as input. The redactor processes these conceptual model outputs to produce Reversa-compatible business rules and alignment artifacts for paridade-guard enforcement.

Can I use these generated SDD artifacts for paridade-guard contract verification?

Yes, you can use the generated SDD artifacts for paridade-guard contract verification. The redactor outputs canonical _visa_sdd artifacts that enforce contracts and map evidence directly to business rules for validation.

What are the limitations of generating SDD artifacts from a domain model?

A limitation of generating SDD artifacts from a domain model is that the output depends entirely on the quality of the conceptual input. The redactor does not resolve domain uncertainties but logs them in ambiguity_log.md for review.