One-click install
npx skills add https://github.com/tmart2322/claude-structure --skill tenet-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tenet-check
Source: https://github.com/tmart2322/claude-structure/tree/main/.claude/skills/tenet-check
Command: npx skills add https://github.com/tmart2322/claude-structure --skill tenet-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of shipping code that drifts from your project's core priorities and invariants, which can cause technical debt, misaligned features, and costly rework by providing a structured, evidence-based review process for all changes.

Core Features & Use Cases

  • North Star Scorecard: Generates a 1-5 score for each applicable project priority (north star) with concrete evidence from the changed code, so you can quantify how well a change aligns with your top goals.
  • Tenet Violation Detection: Identifies all breaks of your project's design and engineering tenets, classifying each as a hard violation (blocking, requires immediate fix) or partial-incomplete (trackable to backlog) to prioritize remediation.
  • Flexible Use Cases: Use it for phase exit reviews, mid-build sanity checks during development, or ad-hoc validation of any change against your project's principles.
  • Example Use Case: Before merging a feature that modifies user data handling, run this Skill to confirm it doesn't violate your "user privacy" tenet and scores well on your top north star of "data protection".

Quick Start

Use the tenet-check skill to review the latest commit diff against your project's north stars and design tenets to get an evidence-backed scorecard and list of any violations.

Frequently Asked Questions about tenet-check

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

FAQPage Schema
How do I check if my code changes violate project design tenets?

To check if code changes violate project design tenets, you review the git diff against documented principles to produce an evidence-backed scorecard and a list of hard or partial-incomplete violations.

What is north star scoring for a software diff?

North star scoring for a software diff quantifies how well code changes align with core business and engineering goals by generating a 1-5 score for each applicable project priority using evidence from the changed code.

How do I validate code alignment before a phase exit review?

To validate code alignment before a phase exit review, apply a principle validation process to the git diff to confirm the changes do not drift from documented north stars and design invariants.

Do I need specific documentation files to run a tenet check?

Yes, you need the project's docs/NORTH_STARS.md, docs/TENETS.md, and docs/ENGINEERING_TENETS.md files alongside the actual git diff of the changes under review to produce the scorecard.

Can I use mid-build sanity checks to catch technical debt early?

Yes, you can run mid-build sanity checks during development to identify breaks of your project's design and engineering tenets early, classifying each as a blocking violation or a trackable backlog item.

Best way to automate principle validation for a git diff?

The best way to automate principle validation for a git diff is to score the changes against documented north stars and design tenets, producing an evidence-backed scorecard that flags misaligned features before merging.