skills.rest
cliffthelin
cliffthelinCOMMUNITY
Explore all skills by this author →
GitHub

reversa-principles

Create or update project principles and generate date-stamped impact reports.

Updated May 13, 2026
Search Tags:#governance#principles#audit history#reversa#template impact#intent alignment#policy-driven development
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-principles-cliffthelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-principles
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/skills/reversa/reversa-principles
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-principles-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create or update a project's enduring principles so every downstream artifact stays aligned with the same higher-order intent.

Core Features & Use Cases

  • Create or Update Principles: Establish a numbered set of core principles (with titles, descriptions, and concrete examples) and maintain a history of changes.
  • Retire Principles Safely: Mark principles as retired (without deleting them) and preserve an audit trail.
  • Generate Human-Readable Impact Reports: For any template impacted by principle changes, produce date-stamped suggestions instead of rewriting templates automatically.

Quick Start

Run this skill by asking to “define principles” for the project so it generates an updated .reversa/principles.md and a date-stamped principles impact report.

Frequently Asked Questions about reversa-principles

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

FAQPage Schema
How do I define core project principles and propagate guidance to downstream templates?▼

You can define core project principles by creating or updating a numbered set of rules, which then generates propagation guidance to ensure affected templates stay aligned with the higher-order intent.

What is a non-destructive approach to retiring project principles?▼

Retiring project principles non-destructively involves marking them as retired rather than deleting them, which preserves a complete audit trail of changes while updating the impact section of your state files.

Can I generate impact reports for templates affected by governance principle changes?▼

Yes, you can generate human-readable, date-stamped impact reports that provide suggestions for affected templates instead of automatically rewriting your template files.

Does this approach enforce sequential numbering for policy-driven development principles?▼

Yes, the system enforces sequential Roman numeral numbering when you create or update enduring principles to maintain consistent structure across your policy-driven development files.

What's the best way to maintain audit history for project governance principles?▼

Maintaining audit history for project governance principles requires reading and writing state files, marking retired principles without deletion, and generating date-stamped impact reports for all template changes.

When should I not use automated template rewriting for intent alignment?▼

You should avoid automated template rewriting when modifying intent alignment, opting instead for non-destructive date-stamped impact reports that suggest changes without directly altering your templates.

Related Skills

Explore More Product & Management Skills→
a2musa2mus

memory-bank

Initialize, read, update, and review structured project memory files across sessions.

Community
Advanced
afsjrafsjr

reversa-principles

Create or update principles.md with before/after hooks and impact reports.

Community
Advanced
sandecosandeco
1.5k

reversa-quality

Audit feature requirements text for clarity, completeness, and consistency.

Community
Intermediate
gotgenesgotgenes
143

markdown-conventions

Enforce project-specific Markdown rules and YAML frontmatter schema during writing.

Community
Intermediate