When should you use it?
- Engineers have finished their analysis and now face a day of assembling the comparison and memo
- A design review keeps asking what happens if cost or weight mattered more
- You are choosing between suppliers, materials or designs and want the reasoning written down
Not for: Running simulations or tests; the skill only reads results that already exist; Making the final call; the memo is a draft for an engineer to sign; Quick choices with two options and one criterion, where a matrix adds nothing
What do you need, and what do you get?
You need
- A matrix of criteria, weights and options, in a spreadsheet, document or typed into the chat
- Analysis or test results for each option, with the document each number comes from
- Hard requirements and constraints, kept separate from the weighted criteria
- Your memo template or a past trade study, if you have one
You get
- A ranked comparison table where each cell shows its raw score, its weighted share and its source
- A sensitivity section naming where the winner changes and which criterion the choice hinges on
- A list of disqualified options, each with the requirement it fails
- A draft decision memo with the recommendation, rejected options and remaining risks
How does it work, step by step?
- Install and onboardAdd Claude for Manufacturing from the Claude plugin directory and complete the setup, including your memo template if you have one.
- Prepare the matrixList criteria with weights that add up to 100, mark each as higher-is-better or lower-is-better, and note which requirements are pass or fail.
- Attach the evidenceGive it the reports or spreadsheets behind each score so every number can be traced.
- Ask for the studySay 'write the trade study' and read the gaps and flip points before the ranking.
- Review and signCheck the memo against your own judgment, edit it and take it to the design review.
The prompt
Our adapted version, written to work in Claude, Claude Cowork and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Write a trade study for {decision} using the matrix in {matrix_file} and the results in {results_files}. Check that the weights add up to 100 and that every option has a score for every criterion. Report any gap instead of filling it, and confirm whether each criterion is better high or better low. Remove any option that fails one of these hard requirements: {hard_requirements}, and list it separately with the reason. Rank the rest with each score's source, then vary the weights and tell me where the winner changes and which criterion the choice depends on. Draft a short decision memo for my review. Do not present it as final.
The original skill is published by anthropics on GitHub (anthropics/claude-plugins-official). Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- Leaving a criterion's direction unstated. If lower cost is scored as better cost the wrong way round, the ranking flips with no visible error.
- Filling empty cells to make the table look complete. The skill reports gaps on purpose; supply the missing result or accept the gap.
- Treating a close finish as a clear win. When two options are within noise, the memo should say so.
- Anthropic labels the plugin a reference implementation it does not actively maintain, so try it on a decision you have already made first.
Our take
Weighted scoring matrices have a credibility problem: somebody picks the weights, the winner falls out of the arithmetic, and the first sharp question in a review exposes how fragile the result is. This skill tackles that directly by making the stress test mandatory rather than a nice extra. If the recommendation changes when cost goes from thirty to thirty-five percent, everyone should know that before the meeting, not during it. We also like that a failed hard requirement removes an option outright instead of just lowering its score, and that an empty cell is reported rather than quietly filled. Those two habits prevent the most common ways a matrix ends up recommending something nobody can actually use. The approach works well beyond engineering; we would use the same discipline to choose a vendor or a software platform. Note that the skill does no analysis itself and the plugin is a reference implementation. In our dry run on a fictional bracket choice among three materials, it disqualified one option on temperature, found the other two about two points apart and showed that a small shift in the mass weight changed the winner, so the memo called the result too close to settle on weights alone.
Where the time goes back: The skill's own description puts the write-up at a day or more after the analysis is done. Getting a sourced table, the sensitivity result and a memo draft in one pass leaves the engineer to review rather than assemble.
FAQ
Is this only for manufacturing?
What does the sensitivity check actually do?
Who made it and what license does it use?
Source and credit
This playbook is based on work by anthropics. We summarize it and link to it and write our own adapted prompt.
- Original
- trade-study-report skill (anthropics/claude-plugins-official, Claude for Manufacturing)
- Creator
- anthropics
- Published on
- GitHub (anthropics/claude-plugins-official)
- Original date
- Nov 12, 2026
- License
- Apache-2.0
- Originally for
- Claude
- AI dry run
- Nov 15, 2026: passed. Dry-run tested by our AI test agent on sample input. Disqualification separate from scoring, correct directions, sensitivity run, close result not oversold.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 15, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under Apache-2.0 by anthropics. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.
Are you the creator? Claim or correct this page.