wabi-sabi

Analyze product decisions through Wabi, Sabi, and Incompleteness lenses.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill wabi-sabi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wabi-sabi
Source: https://github.com/kouko/monkey-skills/tree/main/philosophers-toolkit/skills/wabi-sabi
Command: npx skills add https://github.com/kouko/monkey-skills --skill wabi-sabi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Wabi-Sabi thinking helps teams trim unnecessary complexity while preserving essential value, preventing over-engineering.

Core Features & Use Cases

  • Three lenses: Wabi, Sabi, and Incompleteness to guide decisions.
  • Context-aware guidance for product strategy, architecture, and UX trade-offs.
  • Case-based reasoning with references to common scenarios like API simplification and incremental improvement.

Quick Start

Provide the product decision you want analyzed, and I will apply the three lenses to determine sufficiency and suggested next steps.

Frequently Asked Questions about wabi-sabi

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

FAQPage Schema
How do I analyze a product decision to prevent over-engineering?

To analyze a product decision against over-engineering, apply the three lenses of Wabi, Sabi, and Incompleteness to identify essential value and trim unnecessary complexity. This context-aware method evaluates software architecture and UX trade-offs to ensure core value remains uncompromised.

What is the wabi-sabi approach to software design and minimalism?

The wabi-sabi approach to software design is a framework that uses minimalism and the beauty of incompleteness to guide product decisions. It helps teams find simplicity in imperfection, providing explicit pruning or extension suggestions for architecture and features without losing core value.

How do I decide which features to cut without compromising core value?

To decide which features to cut without compromising core value, use the Wabi and Sabi lenses to evaluate sufficiency based on your project goals and user base. This analysis provides explicit pruning suggestions to trim unnecessary complexity while preserving essential product functionality.

Can I use this method for large-scale architectural choices and small feature cuts?

Yes, you can use this analysis method for large-scale architectural choices and small feature cuts. The framework applies context-aware guidance to software or product decisions of any scale, evaluating API simplification and incremental improvements to determine sufficiency and suggest next steps.

When should I avoid using minimalism to guide product decisions?

You should avoid using minimalism to guide product decisions if the suggested changes would compromise your core value. The framework insists on avoiding suggestions that break essential functionality, ensuring that pruning complexity or applying incompleteness does not degrade the primary user experience.