lego-swap
Swaps one brick for an alternative that fills the same slot, for example a Taylor rule for a managed-FX rule, or an input-output brick for a CGE.
SKILL.md.grok/skills/lego-swap/SKILL.md
GitHub<!-- Generated from .claude/skills/lego-swap/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->
/lego-swap — Lego Swap
Category: Lego (Modular Models) · Primary agent: modeling-methodology-specialist
Swaps one brick for an alternative that fills the same slot, for example a Taylor rule for a managed-FX rule, or an input-output brick for a CGE.
Arguments: whatever the user wrote after the command name.
Purpose
Replace one brick with an alternative that fills the same slot, such as a Taylor rule with a managed-exchange-rate rule, an input-output block with a CGE block, or one Phillips curve with another, and compare the two versions on identical scenarios. Because the swap changes the model's structure, the comparison is a structural-uncertainty exercise and is reported as one.
Use it when testing alternative policy regimes, sectoral structures or behavioral blocks, or assessing how much conclusions depend on a component.
Do not use it when adding a new channel (/lego-add) or removing one (/lego-detach).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- A model.lego.json manifest
- The replacement brick
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
modeling-methodology-specialist— primary agent; coordinates the work and integrates resultseconomic-reasoning-specialist— Frames the economic question and tests whether results make economic sensemodel-validation-specialist— Performs independent model validationpolicy-relevance-specialist— Clarifies the decision, audience and deadline, and reviews outputs for decision-relevance, honest uncertainty and appropriate caveats
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
|---|---|---|
| Alternative | catalog brick in the same slot, new brick | Comparability |
| Scenarios | baseline plus standard shocks, policy-relevant scenarios | Evidence on differences |
| Calibration | keep shared parameters, recalibrate | Attribution of differences |
Workflow
- Dry-run:
python tools/lego.py swap <manifest> <old> <new>. Compare the two bricks: ports lost and gained, new joints, new simultaneous blocks, bridges needed - Resolve errors; if ports consumed by others are lost, either the consumers need stubs or the swap is not like-for-like
- Apply with
--apply --note '<why>' - Run both versions on the same scenarios and tabulate the differences (this is a structural-uncertainty exercise, so report it as such)
- Re-validate the new brick and its neighbours
Checkpoints with the user
- After the dry-run: approve the comparison of ports
- After the comparison table: agree the interpretation
Common pitfalls
- Recalibrating so much that differences cannot be attributed to the swap
- Comparing on different scenarios
- Treating the preferred version's results as certain
Output
Updated model.lego.json and a comparison table in docs/models/<name>/
The comparison table shows both versions on identical scenarios, with explanations of differences through the swapped mechanism.
Gate / verdict
- Like-for-like on the slot, or the differences are documented
- Both versions compared on identical scenarios
- Differences are explained through the swapped mechanism
Suggested next steps
/lego-check/robustness-check