reframe

Converts planning discussions into testable strategic direction judgments with costed options.

2|2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/BTreeMap/SKILLs --skill reframe-btreemap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reframe
Source: https://github.com/BTreeMap/SKILLs/tree/main/reframe
Command: npx skills add https://github.com/BTreeMap/SKILLs --skill reframe-btreemap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often let compatibility fears, migration costs, or inherited constraints dictate direction before the real target is defined, leading to incremental patches that preserve the wrong model. This Skill forces the decision to be reframed at the right altitude before implementation begins. ## Core Features & Use Cases - Constraint Classification: Sorts every inherited constraint into contract, delivery constraint, migration cost, inertia, or unknown, with evidence requirements for each. - Frame-Opening Moves: Applies named techniques like zero-legacy thought experiments, end-state backcasting, and ten-times stress to expose hidden options. - Structured Output: Produces an eleven-section strategic direction judgment covering thesis, confidence, target model, kill list, three costed paths, falsifier, and payoff ledger. - Use Case: When a team debates whether to patch a legacy module or rebuild it, use this Skill to separate the clean target from the migration path and get a falsifiable recommendation with a first proof point. ## Quick Start Ask the agent to reframe the decision on whether to migrate the legacy billing module or keep patching it, and produce a strategic direction judgment.

Frequently Asked Questions about reframe

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

FAQPage Schema
How do I reframe a technical decision that feels too incremental?

State the decision, outcome, horizon, and system boundary, then classify the constraint currently controlling the proposal. Apply a frame-opening move such as the zero-legacy thought experiment to reveal the clean target before comparing conservative, clean, and staged paths.

What is the difference between a contract and migration cost in planning?

A contract requires evidence such as a public API, persisted data, documented integration, or explicit instruction, and must be preserved or renegotiated openly. Migration cost is internal work like caller updates or relearning, which should be estimated and staged but must not dictate the target.

When should I use strategic reframing instead of just planning implementation?

Use it when a local patch is chosen before the target model is stated, when compatibility is preserved without a named contract, or when migration size rejects a direction before its value is assessed. Small proposals are fine when boundary, target, and evidence already support them.

How do I make a strategic recommendation falsifiable?

Define a first proof point that distinguishes your thesis from alternatives, the expected observable signal, and the specific evidence that would force rejection or revision. Defer irreversible commitments until that signal arrives.

What are the limitations of a strategic direction judgment?

It does not cover migration sequencing, rollout, observability, or rollback, which are ordinary engineering work after the target is accepted. It also does not write the product requirements document or decide module-level implementation quality.