wholeness

Evaluate engineering design alternatives using a felt-sense reflection framework.

6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/markacianfrani/armor --skill wholeness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wholeness
Source: https://github.com/markacianfrani/armor/tree/main/skills/wholeness
Command: npx skills add https://github.com/markacianfrani/armor --skill wholeness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves decision paralysis when choosing between two viable technical designs, APIs, or architectures where logical analysis and testing fail to provide a clear winner.

Core Features & Use Cases

  • Felt-Sense Evaluation: Provides a structured, meditative framework to assess which design feels more alive and settled.
  • Ego-Reduction: Guides the user to set aside cleverness and team expectations to identify the design that best aligns with their own engineering self.
  • Use Case: When you are stuck between two equally functional database schemas, use this skill to determine which one feels more intuitive and sustainable for long-term maintenance.

Quick Start

Ask the wholeness skill to help you decide between the two proposed API structures by guiding you through the felt-sense evaluation procedure.

Frequently Asked Questions about wholeness

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

FAQPage Schema
How do I choose between two viable API designs when objective metrics fail?

When objective metrics fail to resolve a design decision, you can evaluate architectural alternatives by applying a felt-sense framework that identifies which option has the highest internal coherence and vitality through structured, ego-neutral reflection.

What is felt-sense evaluation in software architecture and engineering?

Felt-sense evaluation in software architecture is a subjective decision-making technique that assesses which design feels more internally coherent and settled, operating when logical analysis and testing cannot provide a clear winner between technical alternatives.

How do I overcome decision paralysis when comparing database schemas with equal performance?

To overcome decision paralysis comparing database schemas with equal performance, use a meditative framework to set aside cleverness and team expectations, determining which schema feels more intuitive and sustainable for long-term maintenance.

Can I use subjective decision-making for API design and architectural choices?

Yes, you can use subjective decision-making for API design and architectural choices by performing a structured reflection that evaluates internal coherence and vitality when standard metrics like performance and test coverage are inconclusive.

When should I avoid intuition-based design decisions in engineering?

You should avoid intuition-based design decisions when objective metrics like performance metrics or test coverage can provide a clear winner, as this approach is specifically designed for situations where logical analysis fails to resolve architectural or schema alternatives.