reversa-principles

Manage project principles with roman numerals and propagate changes to dependent templates.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-principles-stribus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-principles
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-principles
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-principles-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este skill atua como o guardião dos princípios duradouros do projeto, assegurando consistência entre artefatos e orientando a atualização de templates quando princípios mudam.

Core Features & Use Cases

  • Criar, atualizar e aposentar princípios do projeto com numeração romana (I, II, III, ...), incluindo metadados como título, descrição e data de criação.
  • Propagar impactos para templates dependentes (requisitos, roadmaps, ações) e manter um histórico de alterações.
  • Pode ser executado sozinho ou antes da primeira feature para estabelecer governança e alinhamento entre equipes.

Quick Start

Diga "reversa-principles" para iniciar o fluxo de criação ou atualização de princípios.

Frequently Asked Questions about reversa-principles

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

FAQPage Schema
How do I manage enduring project principles and keep governance templates aligned?▼

Managing enduring project principles involves creating, updating, and retiring guidelines with roman numerals while propagating impacts to dependent templates to maintain artifact consistency and team alignment.

How do I propagate changes to dependent templates when a project principle is updated?▼

Propagating changes to dependent templates is handled by tracking principle lifecycles and generating dated impact reports that identify affected requirements, roadmaps, and related documents.

Do I need to run governance setup before creating features to ensure project alignment?▼

Running governance setup before the first feature establishes enduring principles and team alignment, but it can also be executed independently to manage project principles at any lifecycle stage.

Can I retire outdated project principles and still maintain a history of template changes?▼

Retiring outdated project principles is fully supported, maintaining a history of changes while updating dependent templates and producing dated impact reports in the .reversa state file.

What limitations exist when tracking principle impacts across related documents?▼

Tracking principle impacts across related documents requires reading and writing state to the .reversa directory, limiting automated propagation to connected templates and artifacts within that local state.