Preserving Productive Tensions

Classify decision-making tensions and produce auditable decision records.

8|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill preserving-productive-tensions-gujiachun-rainbow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Preserving Productive Tensions
Source: https://github.com/gujiachun-rainbow/RainClaw/tree/main/.trae/skills/preserving-productive-tensions
Command: npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill preserving-productive-tensions-gujiachun-rainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disagreements in complex projects often reveal valuable context; this Skill helps teams recognize when multiple valid approaches exist and preserve them rather than forcing premature resolution.

Core Features & Use Cases

  • Detects context-dependent tensions and flags when trade-offs are real.
  • Provides a structured pattern (configuration, parallel implementations, or documented trade-offs) to preserve options.
  • Applies to product decisions, architecture choices, and policy discussions across stakeholders.

Quick Start

Provide a configurable option to preserve multiple valid approaches in the current decision.

Frequently Asked Questions about Preserving Productive Tensions

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

FAQPage Schema
How do I handle stakeholder disagreements when multiple valid product priorities exist?

Stakeholder disagreements with valid priorities are managed by preserving productive tensions through configuration options, parallel implementations, or documented trade-offs, preventing premature resolution while maintaining auditable decision records.

What is a productive tension in system design and architecture choices?

A productive tension in system design is a context-dependent trade-off where conflicting approaches hold valid value, requiring preservation strategies like configurable options rather than forced premature resolution.

How do I document trade-offs for cross-team architecture decisions?

Document trade-offs for cross-team architecture decisions by classifying tensions and selecting preservation strategies like configuration or parallel implementations, producing auditable decision records that keep multiple valid paths in play.

Does this approach work for complex product strategy involving multiple stakeholders?

This approach works for complex product strategy by applying a structured framework to classify stakeholder tensions, choose preservation configurations, and generate auditable decision records for valid cross-team trade-offs.

When should I avoid forcing a single resolution for product trade-offs?

Avoid forcing a single resolution for product trade-offs when context-dependent tensions reveal valuable context, indicating multiple valid approaches exist that should be preserved via configuration or documented decisions instead.