reversa-principles

Update .reversa/principles.md and generate dated impact reports for dependent templates.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-principles-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-principles
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-principles
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-principles-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a project’s guiding principles consistent and up-to-date across artifacts by creating or updating enduring principles and propagating adjustments to dependent templates.

Core Features & Use Cases

  • Manage durable project principles: create, update, retire principles with audit-ready history and impact tracking.
  • Propagate changes: automatically identify templates affected by a principle (for example requirements, roadmap, and actions templates) and surface impact notes.
  • Interaction flow: responds to prompts like /reversa-principles, "reversa-principles", "definir princípios" and can run before the first feature to establish governance.

Quick Start

Provide a principle candidate with a title and description, and the system will create or update it while propagating changes to dependent templates.

Frequently Asked Questions about reversa-principles

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

FAQPage Schema
How do I maintain consistent project principles across product management templates?

Project principles are propagated by identifying affected templates and generating a dated impact report, ensuring requirements, roadmaps, and actions reflect governance changes.

What is the best way to track the impact of changing governance principles?

Impact tracking for governance changes is handled by reading and updating .reversa/principles.md, then generating a dated impact report to document before and after states.

How do I create and retire durable product management principles with an audit history?

Retiring or updating principles is managed through the before and after workflow, which records changes and propagates adjustments to dependent templates automatically.

Can I establish governance principles before creating the first product feature?

Establishing principles before feature creation is supported by running the workflow upfront, which sets the foundational rules for all subsequent product artifacts.

How do I propagate change management updates to dependent roadmap and requirements templates?

Propagating updates to templates happens when a principle is modified, ensuring that all dependent artifacts reflect the new change management governance rules.