Agent skill · product strategy · aaaaqwq
Preserving Productive Tensions
Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution
Why this skill is useful
Codifies a decision-making framework for managing architectural tensions that the AI could infer but now doesn't have to guess.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 83 stars on the source repository.
What this skill does
Preserving Productive Tensions Overview Some tensions aren't problems to solve - they're valuable information to preserve. When multiple approaches are genuinely valid in different contexts, forcing a choice destroys flexibility. Core principle: Preserve tensions that reveal context-dependence. Force resolution only when necessary. Recognizing Productive Tensions A tension is productive when: Both approaches optimize for different valid priorities (cost vs latency, simplicity vs features) The "better" choice depends on deployment context, not technical superiority Different users/deployments would choose differently The trade-off is real and won't disappear with clever engineering Stakeholders have conflicting valid concerns A tension needs resolution when: Implementation cost of preserving both is prohibitive The approaches fundamentally conflict (can't coexist) There's clear technical superiority for this specific use case It's a one-way door (choice locks architecture) Preserving both adds complexity without value Preservation Patterns Pattern 1: Configuration Make the choice configurable rather than baked into architecture: When to use: Both approaches are architecturally compatible, switching is runtime decision Pattern 2: Parallel Implementations Maintain both as separate clean modules with shared contract: When to use: Approaches diverge significantly, but share same interface Pattern 3: Documented Trade-off Capture the tension explicitly in documentation/decision records: When to use: Can't preserve both in code, but need to document the choice was deliberate Red Flags - You're Forcing Resolution Asking "which is best?" when both are valid "We need to pick one" without explaining why Choosing based on your preference vs user context Resolving tensions to "make progress" when preserving them IS progress Forcing consensus when diversity is valuable All of these mean: STOP. Consider preserving the tension. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aaaaqwq/sp-preserving-productive-tensions