manifold-m2-tension

To resolve constraint conflicts, you surface tensions between competing requirements and apply resolution methods to balance trade-offs. This skill identifies conflicts where satisfying one requirement makes another harder, categorizing them as trade_off, resource_tension, or hidden_dependency.

A tension in a constraint-first workflow is a constraint conflict occurring when two requirements compete, making simultaneous satisfaction difficult. It manifests as trade-offs between performance and safety, resource allocations, or hidden dependencies across features.

You balance architecture trade-offs by evaluating competing constraints and applying tie-breaking guidance to maintain invariants. This surfaces resource tensions and hidden dependencies early, ensuring explicit phase transitions before proceeding with design decisions.

Yes, you can identify hidden dependencies during architecture design by analyzing constraint conflicts. The skill explicitly categorizes hidden dependencies as a tension type, surfacing them alongside trade-offs and resource tensions in JSON and Markdown output formats.

Constraint tension analysis results are output as combined JSON and Markdown representations. These formats structure the identified trade-offs, resource tensions, and hidden dependencies, providing schema guidance for resolution methods within the workflow.

You should invoke tension analysis during design, architecture, and requirements phases before proceeding with implementation. The skill enforces phase-transition rules, requiring explicit user invocation to surface and resolve constraint conflicts proactively.