skills.rest
Pabloprogramador23
Pabloprogramador23COMMUNITY
Explore all skills by this author →
GitHub

reversa-principles

Defines and propagates durable project principles across templates and roadmapping artifacts.

Updated Jun 6, 2026
Search Tags:#templates#versioning#documentation#governance#principles#project-management#change-history
One-click install
npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-principles-pabloprogramador23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-principles
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa-principles
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-principles-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este skill atua como guardião dos princípios do projeto, definindo regras duradouras que orientam decisões técnicas, arquiteturas e padrões, e propagando mudanças para artefatos dependentes.

Core Features & Use Cases

  • Definição, atualização e aposentação de princípios, com numeração sequencial e histórico.
  • Propagação de impactos para templates dependentes (requirements-template, roadmaps e possivelmente actions-template).
  • Auditoria e registro de alterações com histórico de mudanças.

Quick Start

Defina e gerencie os princípios duradouros do projeto e aplique mudanças aos templates dependentes.

Frequently Asked Questions about reversa-principles

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

FAQPage Schema
How do I define and manage durable project principles for governance?▼

Project principles governance establishes enduring rules that guide technical decisions and architectures. You define, update, and retire principles using sequential numbering while maintaining a full change history for audit traceability.

How do I propagate principle updates to dependent project templates?▼

Propagating principle updates to templates requires applying governance changes directly to dependent artifacts like requirements-templates and roadmaps. This ensures documentation consistency and maintains historical traceability across the project lifecycle.

What is the best way to maintain change history for project management principles?▼

Maintaining change history for project management principles involves recording every update and retirement with sequential numbering. This audit trail satisfies governance requirements and ensures documentation consistency across all related artifacts.

When do I need to update versioning for project principles and roadmapping artifacts?▼

Versioning for project principles and roadmapping artifacts is needed whenever durable rules change. Updating versions propagates impacts to dependent templates, ensuring that all documentation remains consistent with the latest governance decisions.

Can I retire outdated principles without breaking documentation consistency?▼

Yes, retiring outdated principles triggers change propagation to dependent templates while preserving the historical traceability of previous versions. The system updates related roadmapping artifacts to ensure governance consistency throughout the artifact lifecycle.

Related Skills

Explore More Product & Management Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
ArvorCoArvorCo
96

constitution

Create or update a project constitution defining coding principles and governance rules.

Community
Advanced
jmanhypejmanhype
24

spec-kit-workflow

Implement Spec Kit workflow phases and generate project artifacts.

Community
Basic
MohamedSosa19MohamedSosa19

speckit-constitution

Update project constitution templates with versioned governance and placeholder replacement.

Community
Advanced