Triz contradiction

Skill christianmerkwirth/triz-skills/skills/triz-contradiction

TRIZ (Theory of Inventive Problem Solving) Agent Skills for Software Engineering workflows.

Install

npx -y skills add christianmerkwirth/triz-skills --skill triz-contradiction

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
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.

What its author says it does

Copied from the file, not written here

Resolves software engineering contradictions by identifying conflicting parameters and suggesting principles.

SKILL.md

1.7 KB, as published. Nobody here has run it

When to invoke

Invoke this skill when facing a technical trade-off or contradiction where improving one aspect worsens another (e.g., improving speed worsens security).

Inputs needed

Two parameter names or IDs (the parameter to improve and the parameter that worsens), plus an optional module or file scope for the solution.

Reference data used

reference/parameters.md (to resolve names to IDs)
reference/matrix.json (for contradiction cell lookup)
reference/principles.md (to expand principles with software analogies)

Procedure

Receive the inputs (improving parameter, worsening parameter, and optional scope).
Load reference/parameters.md to map the input names to exact parameter IDs.
Look up the contradiction in reference/matrix.json using the IDs.
If the matrix cell is empty, report the gap honestly, list the principles considered based on general heuristics, and STOP. Do not force a fit.
If the matrix cell is populated, present the top 1 to 3 principles with rationale. Expand them using reference/principles.md.
Propose a concrete code change scoped strictly to the user-named module.
Stop. Ask the user to confirm. Do not proceed until they reply.
If confirmed, apply edits only within the specified module scope. Confirm separately before any destructive operation. Do not introduce new major dependencies without explicit opt-in.

Output format

A response that names the principle (by ID and name), the two parameters, the contradiction in a single sentence, and a proposed code diff or plan.