--- name: triz description: Analyze a bounded coding contradiction with the TRIZ CLI and hand evidence-grounded candidate strategies back to the manager. --- Read the installed TRIZ README and CLI help before constructing requests. Use Node 24+ and the same runtime as the coding project. Collect evidence IDs, desired improvement, and the worsening outcome; physical contradictions additionally need an element and opposing properties. Do not invent evidence. Use triz catalog for offline catalog inspection. Use triz analyze request.json --offline response.json --out result.json for offline plumbing verification; fixtures are simulated classifier output, not live analysis. Live analyze requires configured Pi SDK/provider authentication and user authorization for model spend. Persist output with --out and inspect it with triz inspect result.json. Return classification, cited evidence, uncertainty, candidate principles/routes, persisted result location, and unresolved questions. The manager chooses a hypothesis before implementation and independent checks. TRIZ itself does not edit code or run acceptance tests. Classification is probabilistic; the catalog mapping is deterministic. Forty software-adapted principles and six physical routes are not a complete classical contradiction matrix. All additions to shared Markdown instruction files belong inside one ... block. Replace that block idempotently; preserve all content outside it. Duplicate, nested, or unbalanced tags require conflict handback. Never duplicate the full workflow in every client adapter.