preserving-productive-tensions

Document and preserve design tensions to retain architectural flexibility.

130|8|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/sandgardenhq/sgai --skill preserving-productive-tensions-sandgardenhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preserving-productive-tensions
Source: https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/architecture/preserving-productive-tensions
Command: npx skills add https://github.com/sandgardenhq/sgai --skill preserving-productive-tensions-sandgardenhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often face design decisions where multiple approaches are valid and context‑dependent. Forcing an early resolution can lock architecture and lose flexibility. This Skill helps recognize such productive tensions and preserve them for later choice.

Core Features & Use Cases

  • Recognition: Identifies when trade‑offs like cost vs latency represent genuine context‑dependent choices.
  • Preservation Patterns: Offers configuration switches, parallel module implementations, or documented trade‑offs to keep options open.
  • Guidance: Advises when to defer resolution versus when a forced choice is justified, supporting both technical and business stakeholders.
  • Documentation: Provides a structured format to record tensions, contexts, and resolution triggers.

Quick Start

Ask the skill to list and document any design tensions in my current architecture plan.

Frequently Asked Questions about preserving-productive-tensions

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

FAQPage Schema
What is a productive tension in software architecture design?

Preserving design tensions in architecture involves documenting context-dependent trade-offs and configuring selectable modes or parallel modules, allowing stakeholders to defer premature choices and retain deployment flexibility.

When should I defer resolving architectural trade-offs instead of making an immediate decision?

Defer resolving architectural trade-offs when multiple valid approaches exist with outcomes dependent on deployment context, and premature resolution would lock architecture and lose necessary flexibility for stakeholders.

How do I document design tensions to retain architectural flexibility?

Document design tensions by recording the specific trade-offs, deployment contexts, and resolution triggers in a structured format, ensuring stakeholder priorities are satisfied without forcing premature architectural locks.

What patterns help maintain parallel options for trade-off decisions in system configuration?

Maintain parallel options by applying preservation patterns like configuration switches, parallel module implementations, and documented trade-offs to keep architectural choices open until deployment context clarifies priorities.

Can I use configuration switches to manage cost versus latency trade-offs in deployment?

Configuration switches manage cost versus latency trade-offs by acting as selectable modes within the architecture, allowing teams to toggle behaviors based on specific deployment contexts without altering core design.