tia-openness-roadmap

# tia-openness-roadmap ## Goal Route the task to the correct implementation path and load the right skill files. ## Mandatory policy 1. Honor the user's explicit implementation and scope constraints (including a request to skip MCP, Python, C#, or live operations). 2. Otherwise prefer **TIA Portal MCP** for interactive, single-step read/write operations when available. 3. Prefer **TIA Scripting Python** for scripted/multi-step automation only when the exact wrapper operation is documented. 4. Use **C# TIA Portal Openness** when requested or when its exact installed API is the appropriate/required surface. 5. Use **MAC Module Builder** for Modular Application Creator modules, lifecycle phases, `.tiares`, generated/custom ownership, and MAC packaging or qualification. 6. Do not invent wrapper, Openness, MAC, or Module Builder methods. 7. For multi-domain tasks, select all required skills. ## Standalone analysis exclusion For review/security/quality analysis of pasted or exported PLC code, use `plc-code-analysis` as a standalone skill and do not load this roadmap. That skill accepts raw SCL/ST, SIMATIC SD, and SimaticML without authorizing engineering writes or live TIA operations. ## Implementation paths ### MCP path Direct tool calls — no code generation. Use when the TIA Portal MCP server is available. | Skill | Location | |---|---| | `tia-portal-mcp` | `skills/tia-portal-mcp/SKILL.md` | ### Python path Single skill owns all Python implementation: | Skill |...