philosophy-enforcer

Name: philosophy-enforcer
Availability: InStock
Author: treystu

Convert interview input into an enforceable philosophy canon and apply rubric-based gates.

2|Updated Feb 6, 2026

Search Tags:#documentation standards #security posture #engineering governance #philosophy enforcement #product alignment #decision gates #tradeoff matrix

Ready to run

npx skills add https://github.com/Treystu/SCMessenger --skill philosophy-enforcer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: philosophy-enforcer
Source: https://github.com/Treystu/SCMessenger/tree/main/skills/philosophy-enforcer
Command: npx skills add https://github.com/Treystu/SCMessenger --skill philosophy-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents engineering and product changes from drifting away from SCMessenger’s intended mission, trust boundaries, and non-negotiable principles.

Core Features & Use Cases

Required philosophy interview: collects non-negotiable principles and tradeoffs before enforcement.
Enforceable philosophy canon: captures rules in reference/PHILOSOPHY_CANON.md in a testable format.
Gate-based compliance review: scores proposed work against rubric rules and blocks non-negotiable failures with explicit remediations.

Quick Start

Use philosophy-enforcer to evaluate a specific proposed change (for example, a new feature plan, UI behavior change, or architecture modification) by running the interview, updating the canon if needed, and returning an approve/condition/reject verdict with remediations.

Frequently Asked Questions about philosophy-enforcer

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

FAQPage Schema

How do I enforce engineering governance and prevent product drift during feature design?▼

Enforce engineering governance by converting interview input into an enforceable canon and applying rubric-based decision gates to proposed changes. This prevents drift from mission, trust boundaries, security, reliability, and performance posture during feature design and change review.

What is philosophy enforcement for product alignment and how does it work?▼

Philosophy enforcement is a gate-based compliance review mechanism that scores proposed work against rubric rules. It captures non-negotiable principles in a canonical file, evaluates changes, and returns explicit PASS, CONDITIONAL, or FAIL verdicts with required remediations.

How to align architecture and UX changes with security posture using decision gates?▼

Align architecture and UX changes by running a philosophy interview, updating canonical rules, and scoring the proposed work against enforcement rubrics. The gate-based compliance review blocks non-negotiable failures and outputs explicit remediation steps.

Can I use a tradeoff matrix to evaluate documentation standards against engineering governance?▼

Yes, you can evaluate documentation standards by capturing tradeoffs during the philosophy interview and applying them through rubric scoring. The enforcement mechanism checks proposed documentation against the canonical rules and outputs a final approval logic verdict.

What are the limitations of rubric-based compliance review for change management?▼

Rubric-based compliance review requires a completed interview protocol and canonical rule updates before it can function. It cannot evaluate changes without explicit evidence, and all CONDITIONAL or FAIL verdicts demand specific remediations before approval logic proceeds.

Does philosophy enforcement work for reviewing code changes and reliability posture?▼

Yes, philosophy enforcement evaluates code changes by scoring them against the canonical rules and enforcement rubric. It reviews reliability posture alongside mission and trust boundaries, returning an explicit verdict with remediation steps for any non-negotiable failures.