negentropy-lens

Evaluate decisions and architectures by identifying entropic and negentropic indicators.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill negentropy-lens-proleadappt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: negentropy-lens
Source: https://github.com/ProLeadAppt/doggroomerdemo/tree/main/.agents/skills/bencium-negentropy-lens
Command: npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill negentropy-lens-proleadappt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates decisions and architectures through the entropy vs negentropy lens to surface tacit knowledge gaps and drive deliberate, growth-oriented choices.

Core Features & Use Cases

  • Surface tacit knowledge and hidden assumptions during design reviews to reveal unstated constraints.
  • Diagnose entropic indicators (decay, unnecessary complexity) and negentropic indicators (growth, value compounding) across systems and processes.
  • Guide decision-making by surfacing growth opportunities and documenting rationales for chosen paths.

Quick Start

Apply the negentropy lens to your current design decision by mapping entropy indicators and identifying growth opportunities.

Frequently Asked Questions about negentropy-lens

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

FAQPage Schema
How do I use systems-thinking to identify hidden assumptions during architecture reviews?

Apply the entropy vs negentropy lens to architecture reviews to surface tacit knowledge gaps and reveal unstated constraints. This systems-thinking approach evaluates decisions by identifying entropic decay indicators and negentropic growth opportunities.

What is the negentropy lens for evaluating software architecture decisions?

The negentropy lens is a decision-support framework that evaluates architecture through entropy vs negentropy dynamics. It surfaces tacit knowledge gaps by diagnosing entropic indicators like unnecessary complexity against negentropic indicators like value compounding.

How do I diagnose unnecessary complexity and decay in system design?

Diagnose unnecessary complexity and decay by identifying entropic indicators across systems and processes. Use the negentropy lens to map these decay factors against growth opportunities during strategy discussions and design reviews.

Can I use this decision-support approach for team strategy discussions and growth planning?

Yes, you can apply the entropy vs negentropy lens to strategy discussions across teams at decision points. It guides growth-oriented decision-making by surfacing hidden dynamics and producing actionable recommendations for chosen paths.

What is the best way to document design rationales and surface tacit knowledge gaps?

Document design rationales and surface tacit knowledge gaps by evaluating decisions through the negentropy lens. This approach explicitly identifies entropic and negentropic indicators to guide decision-making and record the reasoning for chosen paths.

When should I not use an entropy-based approach for evaluating architecture?

Avoid using the entropy-based approach for architecture evaluation when decision points lack sufficient context for identifying entropic or negentropic indicators. The framework requires explicitly recognizing hidden dynamics and tacit knowledge to produce actionable recommendations.