agentsclimarketplace
Sign in

Architecture tradeoff analysis

Skill planifest/planifest-framework/planifest-framework/external-skills/architecture-tradeoff-analysis

Architecture trade-off analysis workflow for comparing options with explicit criteria, weighting, and sensitivity under uncertainty. Use when multiple viable architecture choices exist and rationale must be defensible; do not use after architecture direction is already fixed.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill architecture-tradeoff-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

Architecture Tradeoff Analysis

Overview

Use this skill to make architecture choices explicit, comparable, and auditable instead of preference-driven.

Scope Boundaries

  • There are several plausible architecture options.
  • Decision stakes are high and reversal is expensive.
  • Teams need a shared basis for selecting one option.

Core Judgments

  • Option quality: whether candidates are realistic for the current context.
  • Criteria set: business and technical dimensions that actually drive success.
  • Weighting model: which criteria dominate and why.
  • Sensitivity: how decision changes when assumptions shift.

Practitioner Heuristics

  • Keep criteria small and high-impact; too many criteria hide real priorities.
  • Separate hard constraints from weighted preferences.
  • Include operational burden and team capability as first-class criteria.
  • Document dominant assumptions and the signals that would invalidate them.

Workflow

  1. Define decision question, constraints, and decision horizon.
  2. Enumerate candidate options and reject non-viable ones early.
  3. Set criteria and weighting aligned to current strategy.
  4. Score options with evidence-backed rationale per criterion.
  5. Run sensitivity analysis on top-weighted criteria and uncertain assumptions.
  6. Select preferred option and document fallback decision path.

Common Failure Modes

  • Scoring hides biased assumptions rather than exposing them.
  • Analysis compares abstract patterns, not implementable options.
  • Sensitivity analysis is skipped, leading to brittle conclusions.

Failure Conditions

  • Stop when decision criteria cannot be agreed.
  • Stop when option scoring lacks evidence for key criteria.
  • Escalate when sensitivity analysis shows no robust winner.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,679. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.