skills.rest
Sovereign-Communication
Sovereign-CommunicationOFFICIAL
Explore all skills by this author →
GitHub

philosophy-enforcer

Review code, documentation, and design changes against predefined product principles.

2|Updated Feb 6, 2026
Search Tags:#code review#change management#philosophy enforcement#product philosophy#change assessment
One-click install
npx skills add https://github.com/Sovereign-Communication/SCMessenger --skill philosophy-enforcer-sovereign-communication
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: philosophy-enforcer
Source: https://github.com/Sovereign-Communication/SCMessenger/tree/main/skills/philosophy-enforcer
Command: npx skills add https://github.com/Sovereign-Communication/SCMessenger --skill philosophy-enforcer-sovereign-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures product and engineering philosophy is consistently applied across all aspects of the SCMessenger application, including code, documentation, and design.

Core Features & Use Cases

  • Philosophy Enforcement: Validates code, documentation, and design changes against a defined set of principles.
  • Interview Protocol: Guides interviews to capture and maintain the core philosophy.
  • Canon Management: Manages and updates the philosophy canon for ongoing reference.
  • Enforcement Rubric: Provides a rubric for evaluating changes against the philosophy canon.
  • Use Case: When reviewing a proposed change, this Skill can be used to assess whether it aligns with the established product philosophy.

Quick Start

Run the philosophy-enforcer skill to assess whether the proposed change to the SCMessenger UI design aligns with the product philosophy.

Frequently Asked Questions about philosophy-enforcer

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

FAQPage Schema
How do I enforce product philosophy during code review and design changes?▼

To enforce product philosophy during code review, you validate proposed changes against a predefined set of principles using an evaluation rubric, ensuring code and design align with core standards.

What is the best way to capture and maintain a product philosophy canon for change assessment?▼

Capturing a product philosophy canon involves interviewing stakeholders to extract core principles, then managing and updating this documentation for ongoing reference during change assessment.

How do I assess if a UI design change aligns with established product philosophy?▼

You assess UI design changes by running the change evaluation against the managed philosophy canon, utilizing the provided rubric to measure adherence to the defined product principles.

Can I use an interview protocol to extract product philosophy from stakeholders?▼

Yes, you can use a guided interview protocol to effectively capture and maintain the core product philosophy from stakeholders, translating insights into an enforceable canon.

Does documentation review require a predefined enforcement rubric to check for principle adherence?▼

Documentation review requires a predefined enforcement rubric to systematically evaluate whether the content aligns with the established product philosophy and defined principles.

Related Skills

Explore More Product & Management Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
StrategicMilkStrategicMilk

API Contract Validation

Compare API contracts to classify changes and generate compatibility reports.

Community
Advanced
TreystuTreystu
2

philosophy-enforcer

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

Community
Advanced
AuroraWebSoftwareAuroraWebSoftware
41

openspec-new-change

Create a new change directory in the OpenSpec framework.

Official
Intermediate