TRIZ Analysis

Systematic innovation audit for software systems, architectures, and workflows.

When to Use

• Auditing a repository for technical contradictions
• Reviewing a CI/CD pipeline or workflow for hidden trade-offs
• Analyzing an architecture for scalability vs. complexity bottlenecks
• Performing a swarm-based TRIZ audit on a project

Input Requirements

• Target Scope: The specific directory, pipeline, or framework to analyze (e.g., scripts/, CI pipeline, agent-coordination skill).

Output Convention

All agent-generated analysis must be written to the analysis/ directory using the following naming convention: analysis/triz-<scope>-YYYY-MM-DD.md