shrivatsas/dev-setup/preserving-productive-tensions
Claude Code and agent skill by shrivatsas/dev-setup
- community
Checking that the SKILL.md file is still in the repository.
Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution
Install
npx vskill@latest install shrivatsas/dev-setup/preserving-productive-tensionsSKILL.md
The same SKILL.md was published earlier as zaka33333-hash/claude-skills/preserving-productive-tensions.
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.
When to Force Resolution
You SHOULD force resolution when:
- Implementation cost is prohibitive
- Building/maintaining both would slow development significantly
- Team doesn't have bandwidth for parallel approaches
- Fundamental conflict
- Approaches make contradictory architectural assumptions
- Can't cleanly separate concerns
- Clear technical superiority
- One approach is objectively better for this specific context
- Not "I prefer X" but "X solves our constraints, Y doesn't"
- One-way door
- Choice locks us into an architecture
- Migration between options would be expensive
- Simplicity requires choice
- Preserving both genuinely adds complexity
- YAGNI: Don't build both if we only need one
Ask explicitly: "Should I pick one, or preserve both as options?"
Documentation Format
When preserving tensions, document clearly:
Examples
Productive Tension (Preserve)
"Should we optimize for cost or latency?"
- Answer: Make it configurable - different deployments need different trade-offs
Technical Decision (Resolve)
"Should we use SSE or WebSockets?"
- Answer: SSE - we only need one-way communication, simpler implementation
Business Decision (Defer)
"Should we support offline mode?"
- Answer: Don't preserve both - ask stakeholder to decide based on user needs
Remember
- Tensions between valid priorities are features, not bugs
- Premature consensus destroys valuable flexibility
- Configuration > forced choice (when reasonable)
- Document trade-offs explicitly
- Resolution is okay when justified
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/preserving-productive-tensions/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/shrivatsas/dev-setup/preserving-productive-tensions)