reversa-principles

Project principles governance involves standardizing durable rules that guide long-lived project decisions. The Reversa principles skill manages this by updating .reversa/principles.md with consistent numbering, ensuring long-lived project principles remain traceable and aligned across dependent templates.

Propagating governance changes safely requires generating a timestamped principles-impact report. This skill assesses affected templates and provides textual suggestions for adjustments, prompting human-in-the-loop decisions rather than automatically rewriting dependent template files.

You need to establish project principles before any feature work starts. This skill runs independently of feature pipelines, supporting governance bootstrapping early to ensure project consistency and prevent template drift before development begins.

Yes, you can retire project principles without losing the audited history. This skill safely retires principles while preserving their historical context within the versioned documentation, maintaining full traceability and consistent numbering in the .reversa/principles.md file.

No, the Reversa principles skill does not automatically rewrite dependent templates. It follows human-in-the-loop conventions by generating a dated principles-impact report with textual suggestions, prompting for human decisions on applying the suggested template adjustments.